Hi Nikita,
while diggin' on the topic in the net, I came across http://namesys.com/bad-block-handling.html, which answers some of my questions, but generates new ones: 1.) What about giving a hint how to gather the blocksize? It's the commonly used 4096, I guess. 4. & 5.) How about loosing a word whats happening behind the scenes here? Right now, I interpret 4. as the necessary step to mark some blocks bad. But why marking the block as "used" first, and as free before running reiserfsck, then. Does this mean, reiserfsck cannot handle bad blocks yet, and I have to restore them afterwards, or what? What does the third parameter "set" in add-bad-block.c? What about the foo file? What happens, if I remove it? My problem is, the fs is populated already, and I've found this in the logs today: Nov 8 13:51:48 shrek kernel: end_request: I/O error, dev 03:09 (hda), sector 40027056 Nov 8 13:52:43 shrek kernel: hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Nov 8 13:52:43 shrek kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=85282224 I was able to isolate two defect sectors on this hd with: dd if=/dev/hda bs=512 count=1 skip=85282224 dd if=/dev/hda bs=512 count=1 skip=85282225 giving I/O errors. It's a IBM-DTLA-307060. I've patched/compiled my 2.4.13-ac7 with linux-2.4.8-reiser-badblocks-1.b.diff already, and will wait for any hopefully enlighting reply before messing with add-bad-block. Thanks in advance, Hans-Peter
