David Brown wrote: > On Wed, Apr 16, 2008 at 10:36:08PM -0500, Todd Walton wrote: >> My father's hard drive ist kaput. The root partition had a hardware >> failure and there's no way on this green earth we will ever recover >> the filesystem information. But this partition had tons and tons of >> pictures on it. It is vital that I get them back.* So I believe I am >> forced into the stream-the-bits-and-look-for-EXIF-data trick. Or >> however that works. I believe we've discussed this before, and I >> intend to have a go at the archives. > > Another approach with reiserfs is to use ddrescue to copy the entire > partition to another drive (do this before you try anything to recover) (or > file), and run resierfsck --rebuild-tree on the file or partition. > > It'll recover pretty much anything on the disk that still has meta data, in > absolutely horrible filenames, but most of the files themselves will be > intact. It does pretty well, but if the bad blocks are directory nodes, > you'll lose the tree structure. > > But, it's a lot better than trying to find picture data embedded in the > data, especially since reiserfs isn't all that good at writing contiguous > chunks. > > Then get a new harddrive, and format it with something other than reiserfs > :-)
A generally accepted recipe that bears repeating, is: cease (ASAP) doing anything which can write to the bad device always make a bitwise copy (maybe even two) _do things_ only to the copy (rescue, repair, experiment..) The more important the data, the more important the above rules. Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
