On Fri, Mar 09, 2007 at 09:40:40AM -0800, Ted Unangst wrote: > > then i'd modify fsck (or maybe write your own, it may be simpler) tool > to start at the filesystem root and scan ahead until it finds an inode > pointing to the bad block.
If the bad blocks produce read errors then tar will tell you the file: tar cf /dev/null /bad_blocks_mount on a read error tar will print out the affected file name. -- Brett Lymn
