Normally we tell people that data corruption bugs must be bad hardware for V3, and this was good advice empirically in the past, however, my vague memory is that there have been more than usual reports of problems with V3 recently. Can you try to reproduce on different hardware, or look through our mailing list traffic for similar problems recently? If you can reproduce it on different memory and CPU or find someone else posting with a similar experience, then I'll ask the guys to try to reproduce it also. Bad hardware can fail for reiserfs and not fail for ext3 because we make the CPU 1-2C hotter and things like fans blocked from turning by cables really can matter for us and not ext3 (a real user experience was just described). In any event, even if it was bad hardware, please let me know.
Hans Michael Barnwell wrote: > Hi, > > Jan Kara wrote: > > <snip> > >> Hmm, that is really strange. Do the files have the same size? Do you >> get an error also if you just create file full of zeros? If so, how do >> the differences look like (e.g. any signs of flipped bits or so?). >> > > [EMAIL PROTECTED]:/tmp$ dd bs=1024 count=1000k if=/dev/zero of=./1GB.tst > 1024000+0 records in > 1024000+0 records out > 1048576000 bytes transferred in 61.578769 seconds (17028207 bytes/sec) > [EMAIL PROTECTED]:/tmp$ ls -l 1GB.tst > -rw-r--r-- 1 michael michael 1048576000 2006-01-15 20:51 1GB.tst > [EMAIL PROTECTED]:/tmp$ md5sum 1GB.tst > e5c834fbdaa6bfd8eac5eb9404eefdd4 1GB.tst > [EMAIL PROTECTED]:/tmp$ ls -l /home/michael/1GB.tst > -rw-r--r-- 1 michael michael 1048576000 2006-01-15 20:54 > /home/michael/1GB.tst > [EMAIL PROTECTED]:/tmp$ md5sum /home/michael/1GB.tst > 92c51557041ebd6424b4467a878c9f44 /home/michael/1GB.tst > > I looked at the file in /home/michael/1GB.tst with xdd for about 5 > minutes but couldn't see anything but zeros - I'm not sure how to > search through a binary file for non-zero bytes. > > So yes, error if the file is all zeros and they have the same size. > > Thanks, > > Michael Barnwell. > >
