Reiserfs and badblocks?
The questions I have is to clearify a problem encountered a few days ago:
Basic setup:
- Linux Kernel 2.4.3-20mdk (Mandrake 8.0 I believe)
- LVM configured
- Reiserfs on top of LVM (90 GB)
The setup had worked for a few months flawlessly.
But after creating an archiver (the archiver is supposed to find new files and copies them into an _ARCHIVE_ directory) script which is triggered via cron a lot of "stat's" where done on the filesystem. They might have caused the messages I'm getting know when accessing certain files:
Feb 25 18:17:20 apu kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Feb 25 18:17:20 apu kernel: hda: dma_intr: error=0x40 {
UncorrectableError }, LBAsect=70366, sector=70280
Feb 25 18:17:20 apu kernel: end_request: I/O error, dev 03:01 (hda),sector 70280
I assume my hard disk /dev/hda has bad blocks which have not been used before.
Here are my questions:
1) Can a bug in a filesystem, LVM or VFS cause -directly or subsequently- such an I/O Error?
2) If this is not a filesystem problem, how can I protect my maschine from such errors? Are their hard drives out there _without_ badblocks, or how do modern drives handle badblocks anyway?
3) If I had say ext3 installed, how would ext3 handle such badblocks (assuming they weren't there when the drive was formatted).
Thank you very much for your support. Please CC your reply to my email, since I'm not a subscriber to linux-kernel.
With regards,
;Martin Rode
Signature · 13 lines
Dipl.-Kfm. Martin Rode [email protected] Zeroscale GmbH & Co. KG Frankfurter Allee 73d 10247 Berlin http://www.zeroscale.com/ http://www.programmfabrik.de/ Fon +49-(0)30-4281-8001 Fax +49-(0)30-4281-8008 Funk +49-(0)163-5321400
Quoted 22 lines · Martin Rode
The questions I have is to clearify a problem encountered a few days ago:
Basic setup:
- Linux Kernel 2.4.3-20mdk (Mandrake 8.0 I believe)
- LVM configured
- Reiserfs on top of LVM (90 GB)The setup had worked for a few months flawlessly.
But after creating an archiver (the archiver is supposed to find new files and copies them into an _ARCHIVE_ directory) script which is triggered via cron a lot of "stat's" where done on the filesystem. They might have caused the messages I'm getting know when accessing certain files:
Feb 25 18:17:20 apu kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 18:17:20 apu kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=70366, sector=70280 Feb 25 18:17:20 apu kernel: end_request: I/O error, dev 03:01 (hda),
Quoted 4 lines
sector 70280
I assume my hard disk
/dev/hdahas bad blocks which have not been used before.
I'd backup if I were you. A thing you can try turning off UDMA on both the kernel and bios, and see if it improves the situation. You can then do a badblocks run and mark with fsck.
But if you havent changed anything, your HD is quite wounded.
Signature · 4 lines
____/| Ragnar Højland Freedom - Linux - OpenGL | Brainbench MVP \ o.O| PGP94C4B2F0D27DE025BE2302C104B78C56 B72F0822 | for Unix Programming =(_)= "Thou shalt not follow the NULL pointer for | (www.brainbench.com) U chaos and madness await thee at its end." [20 pend. Mar 10]