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.
> 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).
--
Nadav Har'El | Thursday, Mar 20 2003, 16 Adar II 5763
[EMAIL PROTECTED] |-----------------------------------------
Phone: +972-53-245868, ICQ 13349191 |"I don't use drugs, my dreams are
http://nadav.harel.org.il |frightening enough." -- M. C. Escher
=================================================================
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]
