I did turn off a couple of the "PARANOIA" switches in the nfs source
to reduce the size of our /var/log/messages file, but we haven't seen
a thing.
My quad xeon had 5 9.2 gig ultra-2 scsi drives and gets beat to death
all the time with lots of file I/O, 400% cpu busy, etc.. and I haven't
had any file corruption at all...
Robert Hyatt Computer and Information Sciences
hyatt@cis.uab.edu University of Alabama at Birmingham
(205) 934-2213 115A Campbell Hall, UAB Station
(205) 934-5473 FAX Birmingham, AL 35294-1170
On Wed, 4 Aug 1999, Jeffrey Mark Siskind wrote:
> 2.2.10 has known fs-corrupting bugs.
>
> This scares me. I just upgraded 14 machines to 2.2.10 with file servers among
> them.
>
> Can somebody fill me in:
>
> 1. Does it affect all motherboard/chipset/cpu types?
> 2. Does it affect smp, non-smp, or both?
> 3. Does it affect scsi, ide, or both?
> 4. Will files contents get corrupted without being detectable by fsck?
> (I.e if my disk fscks can I be assured that the bug hasn't stricken and
> hasn't corrupted my files behind my back?)
> 5. Will files that aren't written be corrupted?
> 6. Which 2.2 kernels does this affect? How far do I need to go back to avoid
> the bug?
>
> Jeff (http://www.neci.nj.nec.com/homepages/qobi)
> -
> Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
> To Unsubscribe: send "unsubscribe linux-smp" to majordomo@vger.rutgers.edu
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/