Nadav Har'El wrote:
On Thu, Mar 20, 2003, Michael Sternberg wrote about "backup woes":
/dev/hda6: Can't read next inode while scanning inode #2453824
After that dump quits without finishing backup.
The questions are: 1. What that mean ? Is my hard disk is gone ?
Maybe you should run fsck on the disk to check it... You should unmount it first (not trivial if this is your /bin's filesystem). You can use it with the "-c" option to also check the disk for bad blocks (see e2fsck(8)). You might need to use the "-f" option to fsck, if the filesystem is claimed to be "clean" without any checking being done.
Might be easier to log in as root, init 1 <enter root pwd> <do fsck as you suggest> if all OK, init 3 or 5 else real Oy vay.
This is something of a last resort that I've used once or twice after a serious crash (usually power failure), but if there was something really wrong, it'll screw up the /dev/hda6 forever. (Moral of the story: Keep /home on its own logical partition. If it goes at least you have your system and it a system partition goes e.g. /bin, /usr, at least you have your data.)
2. How can I check out to what file belongs this inode ?
A slow method would be
find /whatever/mountpoint -inum 123456
I don't know of a faster way (there might not be, considering that in Unix
the same inode can be used by several files, via hard links).
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
