lkml.org 
[lkml]   [1997]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Again - inode races [PATCH] Re: Corrupted inode list?
    I just had problems of simular nature.  I have not had hardware problems
    in the past with this drive or machine. I have however just upgraded to
    glibc-2.0. The problems started after when I had a bunch of kernel memory
    free pool errors, I have also just started some java development.
    Downgrading to 2.0.28 did not help.

    Just adding my data-point.
    would oop's help?

    tim...

    some info.
    processor : 0
    cpu : 586
    model : Pentium 75+
    vendor_id : GenuineIntel
    stepping : 12
    fdiv_bug : no
    hlt_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid : yes
    wp : yes
    flags : fpu vme de pse tsc msr mce cx8
    bogomips : 53.25

    CONFIG_EXPERIMENTAL=y
    CONFIG_MODULES=y
    CONFIG_KERNELD=y
    CONFIG_NET=y
    CONFIG_PCI=y
    CONFIG_PCI_OPTIMIZE=y
    CONFIG_SYSVIPC=y
    CONFIG_BINFMT_AOUT=y
    CONFIG_BINFMT_ELF=y
    CONFIG_M586=y
    CONFIG_BLK_DEV_FD=y
    CONFIG_BLK_DEV_IDE=y
    CONFIG_BLK_DEV_IDEDISK=y
    CONFIG_BLK_DEV_IDECD=y
    CONFIG_BLK_DEV_TRITON=y
    CONFIG_INET=y
    CONFIG_PATH_MTU_DISCOVERY=y
    CONFIG_IP_NOSR=y
    CONFIG_SKB_LARGE=y
    CONFIG_NETDEVICES=y
    CONFIG_NET_ETHERNET=y
    CONFIG_NET_ISA=y
    CONFIG_NE2000=y
    CONFIG_PPP=y
    CONFIG_MINIX_FS=y
    CONFIG_EXT2_FS=y
    CONFIG_FAT_FS=y
    CONFIG_MSDOS_FS=y
    CONFIG_PROC_FS=y
    CONFIG_NFS_FS=y
    CONFIG_ISO9660_FS=y
    CONFIG_SERIAL=y
    CONFIG_MOUSE=y
    CONFIG_PSMOUSE=y
    CONFIG_APM=y
    CONFIG_APM_CPU_IDLE=y
    CONFIG_APM_DISPLAY_BLANK=y
    CONFIG_SOUND=y

    Modules seems to be broken on my machine.

    On Tue, 4 Feb 1997, Stephen C. Tweedie wrote:

    > Hi again,
    >
    > On 30 Jan 1997 16:04:14 -0800, Steven L Baur <steve@miranova.com> said:
    >
    > > ...
    > >> However, having said all that, we've been bitten by races in this part
    > >> of the code before, so if you _can_ demonstrate a real race condition
    > >> in the VFS itself, please do let me know...
    >
    > > I don't know how I can demonstrate a problem, but something is
    > > definitely still amiss. I just got bitten by this bug again a few
    > > hours ago after eight days of using the patch in this thread and
    > > 2.0.28:
    >
    > > Jan 30 13:04:06 altair kernel: EXT2-fs warning (device 16:02): ext2_free_inode: bit already cleared for inode 286988
    > > Jan 30 13:04:06 altair last message repeated 2 times
    >
    > > The total lossage this time was zeroed inodes 286,985 through 286,988
    > > and 364,586 through 364,588. :-(
    >
    > Indeed --- I doubted very much that the patch would actually fix
    > anything. The fact that you are seeing such regular patterns of
    > corruption, and that they are only appearing on one of your three
    > drives, really does suggest that it is a case of borderline hardware
    > problems rather than software. I have seen similar sporadic patterns
    > of bitmap corruption in the past myself, and it has always turned out
    > to be hardware related.
    >
    > If all of your disks are IDE, then you could at least start to narrow
    > down the problem by moving the problem disk to the other IDE channel.
    >
    > Cheers,
    > Stephen.
    >


    \
     
     \ /
      Last update: 2005-03-22 13:38    [W:0.025 / U:0.068 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site