2.6.15 is having difficulty handling bad blocks

[Jin Suh]

We have a following report dealing with bad blocks. Any help would be
appreciated.

2.6.15 is having difficulty handling bad blocks. Numerous tests on 2 different
drives with bad blocks have resulted in either the imaging or verify process
failing, or (on one of the drives tested) a kernel panic, when the process hits
the bad blocks. System messages show typical error messages followed by an "hde
lost interrupt" error when the process fails.

The problem is somewhat inconsistent as one of the drives tested did properly
pad the bad blocks and complete the process.

Testing of the same drives with same commands with the Linux 2.4.29-rc1 show
that it handles the bad blocks properly, padding as desired.

Testing on the class FC4 install (2.6.14-1.1656_FC4i1smp), with the same dcfldd
command as the boot CD, results in the same failed behavior.

Varying the block size (512 and 1024) has no apparent effect, process still
fails on bad blocks.

dd_rescue also tested with the same failed result

Drives tested:

WD WD100 10 GB, LBA 19541088, s/n:WMA6K3772662 - imaging and verifying
processes failed when encountering bad blocks

WD WDC AC2540H 540 MB, LBA 1056384, s/n: WD-WT2610005691 - imaging and
verifying processes completed (padded bad blocks)

Seagate ST36451A 6448 MB, LBA 12594960, s/n: JG297669 - imaging and verifying
processes failed when encountering bad blocks



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/