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
-- Dipl.-Kfm. Martin Rode martin.rode@zeroscale.comZeroscale 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/