Boot messages tell me I have one bad block on /dev/hda9 which is /home.
Bad Block Number 385247 (Slackware 10.1, kernel 2.16.16.16 reiserfs3.6.18)

Since it is only 1 block I decided to try writing to the bad block to see if will be reallocated from a reserve (one option suggested by the boot messages).

But first...

I did a bad block listing after umounting the partition (but stayed in multi-user mode) first getting reiserfs-blocksize 4096 from debugreiserfs:
#debugreiserfs /dev/hda9
#badblocks -b 4096 /dev/hda9

This now tells me I have 2 bad blocks:
Numbers: 385247 385216

Since I will be destroying data in the bad blocks I'd like to know what dirs and files the 385216 block corresponds to. Also, I'd like to ensure that it is a bad block before I do write to it.

I have identified the dirs for the first block [385247] using the inode numbers in syslog. Seems that they correspond to an encrypted dir and its counterpart.

Questions:
1.How do I get the inode number(s) from the block number 385216 so I can get the files from the inode? (Read that icheck (& ncheck) might work but I think they are Debian.)
2.Alternatively, how might I get the inode nos from the LBA for block no 385216?


Thanks

Modern drives hide bad blocks from the filesystem until things are getting really bad.
Have a look at the smartmon status of your drive and also get the (usually dos mode) diagnostic test software from your drive maker.
If the drive is on its way out there is nothing to be done but buy a new one quickly and get your data off before its too late

Regardless of whether the disk is replaced, I would still like to know
where the bad block is in the file system (then I can check my backup
is OK (I have already done a tar of the whole disk) The files on the bad
block that I have identified I don't mind losing.
I know reiserfs people advise replacing the disk as a first option, but also suggest writing to it to reallocate the bad sector.
The disk is only a few months old, so I'd like to try this first since, if it worked and continued to work, this would be quicker.
As to the suggestion of running smartcl, I had already done the short test, though it didn't show any errors. I assume the drive maker software would not identify the files affected, which is what I need at the moment.
I know there is some question about the ability of Reiserfs to recover from bad blocks, I never had a problem before with the ext2 fs. After this I am wondering whether to switch to ext3.

Anyway, does anyone know the answer to the first questions???.