On 27/12/99 Daniel Barclay wrote:
>
>Has anything changed recently on your system? (Is the disk new?
>Have you enabled bus-mastering recently (e.g., reconfigured or upgraded
>the kernel)?)
the hardware has not changed at all, the kernel I upgraded to 2.2.13
when i installed the system over a month ago, and it ran flawlessly
until now. the configuration is pretty much the same as i used for
2.2.10,11,12 for which i had no problems (this was under redhat,
before i reinstalled the system as a debian system.)
>I got similar-sounding extreme disk corruption (at least three times) after
>adding a new disk drive, but only when running a program of mine that created
>a lot of small files and directories.
it appeared to occur right after that cron job ran finds that
recursed the entire filesystem, but what is strange is those same
cron jobs were running all the previous time that month, with same
kernel and such with no errors...
>My kernel log (/var/log/message.log) had error like this:
i had very few errors in the logs and they were not about hardware
issues like that, i neglected to save or write them down
unfortunately but they were errors about duplicate blocks on inode or
some such things, here is a sample of the fsck output:
Pass 1: Checking inodes, blocks, and sizes
Duplicate blocks found... invoking duplicate block passes.
Pass 1B: Rescan for duplicate/bad blocks
Duplicate/bad block(s) in inode 65: 50375
Duplicate/bad block(s) in inode 66: 50376
Duplicate/bad block(s) in inode 67: 50377
Duplicate/bad block(s) in inode 68: 50378 50379 50380
Duplicate/bad block(s) in inode 69: 50381 50382 50383 50384 50385
Duplicate/bad block(s) in inode 70: 50386 50387 50388 50389 50390
Duplicate/bad block(s) in inode 71: 50391 50392 50393 50394
Duplicate/bad block(s) in inode 72: 50395 50396 50397 50398 50399
50400 50401 50402 50403 50404 50405 50406 50407 50408 50409 50410
50411
Duplicate/bad block(s) in inode 73: 50412 50413 50414 50415 50416
Duplicate/bad block(s) in inode 74: 50417 50418 50419 50420 50421
Duplicate/bad block(s) in inode 75: 50422 50423 50424
Duplicate/bad block(s) in inode 76: 50425 50426 50427 50428
Duplicate/bad block(s) in inode 77: 50429 50430 50431 50432 50433
Duplicate/bad block(s) in inode 78: 50434
Duplicate/bad block(s) in inode 79: 50435
that goes on for a couple hundred pages worth then goes into other errors,
I just wiped the disk and ran dd if=/dev/zero of=/dev/hda then cat
/dev/hda > /dev/null and got no errors on either (this is how i test
floppies and it does well at showing bad floppies)
>Is 2.2.13 the newest 2.2.x kernel? If not, you might upgrade to
>the newest. If so, look for the directory
>pub/linux/kernel/people/hedrick on www.kernel.org or mirrors.
>It looks like you might want the file ide.2.2.13.19991111.patch.gz.
>
>(I have a copy at the moment, so if you can't find it, I can e-mail it
>to you.)
I am running the 2.2.13 kernel that was posted to kernel.org when it
was released, I was not aware of any patches to it..
its strange because i run the same kernel configured the same way
(sans sound support) on another machine using IDE disks and have no
problems with fs corruption. even when doing very disk intensive
things, recursive finds, copying 600+ MB of large files from one
place to another, detaring huge .tar files etc, i do not do anything
nearly so disk intensive on this other box and yet total fs hosage :(
thanks
btw the only errors i ever get out of fsck on my other box (the one
that is doing fine) is this:
/dev/hda7: Setting filetype for entry 'showq' in
/spool/postfix/public (45244) to 6.
/dev/hda7: Setting filetype for entry 'cleanup' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'rewrite' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'bounce' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'defer' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'smtp' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'error' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'local' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'cyrus' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'uucp' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'ifmail' in
/spool/postfix/private (100745) to 6.
/dev/hda7: Setting filetype for entry 'bsmtp' in
/spool/postfix/private (100745) to 6.
/dev/hda7: 3665/102800 files (1.6% non-contiguous), 69820/409601 blocks
I get those on both machines actually, every time i run fsck, its not
postfix since i also get the same thing for the xfs sockets created
in /tmp (on a different partition)
Ethan
