Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got some bad sectors pending reallocation (based on smartmontools reports), and I'm trying to find out which file the sector is currently related to so that I can restore from a backup or such or determine how safe it is to write over it.

# debugfs 
 debugfs 1.41.14 (22-Dec-2010) 
 debugfs:  open /dev/sda3 
 debugfs:  testb 28475580 
 Block 28475579 marked in use 
 debugfs:  icheck 28475580 
 icheck: Can't read next inode while doing inode scan 
 debugfs:  quit

After the calculations, the block in question is 28475579. testb says it's in use, but icheck keeps on giving me that error "Can't read next inode while doing inode scan". What is the cause for this?

share|improve this question
It probably means the bad sector is part of the inode table. So you have lost 4 inodes. But if you overwrite the entire block (not just the bad sector), you will have lost 32 inodes. – kasperd Sep 8 '15 at 7:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.