Identifying an ext3 file given a block or inode

[Steven W. Orr]

On Friday, Oct 27th 2006 at 12:13 -0400, quoth Michael ODonnell:

=>
=>When looking at the output of fsck as it works on a wounded
=>ext3 filesystem I'm wishing I knew which files are associated
=>with the duplicate blocks and corrupted inodes it's reporting.
=>It seems that I recall somebody here recently mentioning a tool
=>that could figure out that sort of thing but I can't find the
=>msg in either my own archives or on www.gnhlug.org
=>
=>I do know about this:
=>
=>   find /fubar -inum 123445
=>
=>...for finding files by their inode number, but thought I'd
=>heard mention of a more sophisticated, ext3-specific tool.

If you're looking for ext{2,3} related tools look at debugfs, dumpe2fs, 
filefrag. filefrag looks promising but this should be enough to get you 
started.


This is the whole set of executables that come with the package:

/sbin/badblocks
/sbin/blkid
/sbin/debugfs
/sbin/dumpe2fs
/sbin/e2fsck
/sbin/e2image
/sbin/e2label
/sbin/findfs
/sbin/fsck
/sbin/fsck.ext2
/sbin/fsck.ext3
/sbin/logsave
/sbin/mke2fs
/sbin/mkfs.ext2
/sbin/mkfs.ext3
/sbin/resize2fs
/sbin/tune2fs
/usr/bin/chattr
/usr/bin/lsattr
/usr/bin/uuidgen
/usr/sbin/ext2online
/usr/sbin/filefrag
/usr/sbin/mklost+found


-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net