reiserfsck --rebuild-tree failure

2007-01-28 Thread clara
I have three drives: one data drive, hdb, with one ext2 partition and two system drives, hda and hdc, each with swap and two reiserfs partions, one with root hda3/hdc3 and one with data files hda2/hdc2. I can normally boot either system from the suse boot menu. I had a bootfailure of Suse 8.1 on

reiserfsck --rebuild-tree failure

2006-04-19 Thread majek
Hi I have problem while rebuilding reiserfs (standing on lvm). Lvm contains 3*400GB drives, ata. The device was 95% full - about 1.1TB. [EMAIL PROTECTED]:/dev/devil-linux]# reiserfsck -y --rebuild-tree data reiserfsck 3.6.19 (2003 www.namesys.com) Pass 0: Loading on-disk bitmap .. ok, 285948016

Re: reiserfsck --rebuild-tree failure

2005-11-17 Thread Vitaly Fertman
On Wednesday 16 November 2005 20:27, iv wrote: i'm following an advice to send a bug report about failed reiserfsck --rebuild-tree found at http://www.namesys.com/faq.html#rebuild-tree. i tried to compile the newest reiserfsprogs-3.6.15-pre1 but it fails use reiserfsprogs-3.6.19.tar.gz from

Re: reiserfsck --rebuild-tree failure

2005-11-17 Thread Carles Pina i Estany
Hi, On Nov/17/2005, Vitaly Fertman wrote: i've got a lot of error massages in kern.log: kern.log. obvious, there are badblocks: badblocks.log. check out www.namesys.com/bad-block-handling.html interesting, I didn't know this feature. It works in Reiser 3 and 4? (It seems that yes, just

Re: reiserfsck --rebuild-tree failure

2005-11-16 Thread Sander
iv wrote (ao): obvious, there are badblocks: badblocks.log. i still can read from damaged partition. when i run `strings /dev/hdc3` i get plently of text. the question is if there is a way to mount the partition. dd_rescue the whole partition to another disk and reiserfsck the resulting

Mount fails after reiserfsck --rebuild-tree failure

2003-06-19 Thread Giuliano Luppi
Estimated sirs, after experiencing some problems accessing files on a reiserfs file system (SuSE linux 8.1, kernel 2.4), I tried reiserfsck –rebuild-tree. Since the problem resulted to be in the hardware, it failed, leaving me with an unmountable partition (root inode set to 0) As suggested in