On 7/30/07, Boyd Stephen Smith Jr. <[EMAIL PROTECTED]> wrote: > 5) If (2) indicates corruptions that can only be corrected by --rebuild-tree > a) If you suspect your hardware is failing -- replace it. reiserfs doesn't > like bad hardware and continuing the recovery process on it will likely cause > more pain that it will alleviate. > b) Begin praying.
This guy knows his stuff. Last time I used reiser I didn't pray enough to keep it going > c) Have you ever stored a different reiserfs on this block device without > erasing it? This includes uncompressed lookback files in this or previous > filesystems. If so, you are likely in much trouble. My best suggestion is > to try and overwrite such data, but how to find it? Good question. Yeah ... definitely take note of that sucker , if you ever did dd if=/dev/someresierdrive of=/home/somemountedreiserfs/img for backup purposes, just either give up the idea of a rebuild tree, or find a young lamb to slaughter, ,,,, just in case praying ain't sufficient. > d) reiserfsck --rebuild-tree /dev/block > e) Read warning, type "Yes" (the whole word) to continue. > f) Continue praying. And/Or maybe fast a few days first. This is important stuff :S > g) Go to (2), if it completes at all you can stop praying, for now. > 6) Healthy reiserfs, perhaps with some misplaced data in lost+found. and possibly random files all over your file system who's names have no resemblance to their content, which used to be in an uncompressed reiser, and now is unpacked all over its host FS. all the best :) > > -- > Boyd Stephen Smith Jr. ,= ,-_-. =. > [EMAIL PROTECTED] ((_/)o o(\_)) > ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' > http://iguanasuicide.org/ \_/ > > -- Kent ruby -e '[1, 2, 4, 7, 0, 9, 5, 8, 3, 10, 11, 6, 12, 13].each{|x| print "enNOSPicAMreil [EMAIL PROTECTED]"[(2*x)..(2*x+1)]}' -- [EMAIL PROTECTED] mailing list
