reiserfsck (3.6.19) --rebuild-tree failed

reiserfsck (3.6.19) --rebuild-tree failed

[grossnik.mailinglists]

Dear all
I did a big mistake:
- I got bad blocks on my home partition
- I created a badblock file using:
  badblocks -b 4096 -s -v -o /root/hda3.bad /de/hda3
- I tried to use reiserfstune to apply bad blocks:
 reisefstune -B /root/hda3.bad /dev/hda3
- The tool said I have to use reiserfsck =>

$ reiserfsck --rebuild-tree --badblocks /root/hda3.bad /dev/hda3

Then I provides "Yes"

after 25% the --rebuild-tree  stopped saing that there were bad blocks and that I've to provide the -B option and a badblock file.

But this is what I did (using --badblocks /root/hda3.bad).

Now /dev/hda3 can't be mounted (rood inode is set to -1).

I would be VERY happy if I could mount the partition read only!

What can I do?

Many Thx in advance

Bruno

Kernel is 2.6.15 (Debian)
reiserfsck -V => 3.6.19

debugreiserfs /dev/hda3:
Filesystem state: consistent

/home: Reiserfs super block in block 16 on 0x303 of format 3.6 with standard journal
Count of blocks on the device: 4883760
Number of bitmaps: 150
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 4883760
Root block: 0
Filesystem is clean
Tree height: 65535
Hash function used to sort names: "r5"
Objectid map size 614, max 972
Journal parameters:
	Device [0x0]
	Magic [0x78b2a94e]
	Size 8193 blocks (including 1 for journal header) (first block 18)
	Max transaction length 1024 blocks
	Max batch size 900 blocks
	Max commit age 30
Blocks reserved by journal: 0
Fs state field: 0x0:
sb_version: 2
inode generation number: 500386
UUID: f4fcb46d-04da-43c9-918d-2ef00f8d8412
LABEL: /home
Set flags in SB:
	ATTRIBUTES CLEAN



cat /root/hda3.bad
4602176
4602179
4602180
4602181
4602182
4602183
4602185
4602186
4602187
4602188
4602189
4602190
4602191
4602193
4602194
4602195
4602196
4602197
4602198
4602199
4602201

Re: reiserfsck (3.6.19) --rebuild-tree failed

[Vladimir V. Saveliev]

Hello

On Friday 08 September 2006 13:51, grossnik.mailinglists@hispeed.ch wrote:
> Dear all
> I did a big mistake:
> - I got bad blocks on my home partition
> - I created a badblock file using:
>   badblocks -b 4096 -s -v -o /root/hda3.bad /de/hda3
> - I tried to use reiserfstune to apply bad blocks:
>  reisefstune -B /root/hda3.bad /dev/hda3
> - The tool said I have to use reiserfsck =>
>
> $ reiserfsck --rebuild-tree --badblocks /root/hda3.bad /dev/hda3
>
> Then I provides "Yes"
>
> after 25% the --rebuild-tree  stopped saing that there were bad blocks and
> that I've to provide the -B option and a badblock file.
>
> But this is what I did (using --badblocks /root/hda3.bad).
>
> Now /dev/hda3 can't be mounted (rood inode is set to -1).
>
> I would be VERY happy if I could mount the partition read only!
>
> What can I do?
>
> Many Thx in advance
>
> Bruno
>
> Kernel is 2.6.15 (Debian)
> reiserfsck -V => 3.6.19
>
> debugreiserfs /dev/hda3:
> Filesystem state: consistent
>
> /home: Reiserfs super block in block 16 on 0x303 of format 3.6 with
> standard journal Count of blocks on the device: 4883760
> Number of bitmaps: 150
> Blocksize: 4096
> Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
> blocks): 4883760 Root block: 0
> Filesystem is clean
> Tree height: 65535
> Hash function used to sort names: "r5"
> Objectid map size 614, max 972
> Journal parameters:
> 	Device [0x0]
> 	Magic [0x78b2a94e]
> 	Size 8193 blocks (including 1 for journal header) (first block 18)
> 	Max transaction length 1024 blocks
> 	Max batch size 900 blocks
> 	Max commit age 30
> Blocks reserved by journal: 0
> Fs state field: 0x0:
> sb_version: 2
> inode generation number: 500386
> UUID: f4fcb46d-04da-43c9-918d-2ef00f8d8412
> LABEL: /home
> Set flags in SB:
> 	ATTRIBUTES CLEAN
>
>
>
> cat /root/hda3.bad
> 4602176
> 4602179
> 4602180
> 4602181
> 4602182
> 4602183
> 4602185
> 4602186
> 4602187
> 4602188
> 4602189
> 4602190
> 4602191
> 4602193
> 4602194
> 4602195
> 4602196
> 4602197
> 4602198
> 4602199
> 4602201

please run 
for i in `cat /root/hda3.bad`; do debugreiserfs -1 $i /dev/hda3 > /dev/null; 
done

and let me see the output

Re: reiserfsck (3.6.19) --rebuild-tree failed

[Vladimir V. Saveliev]

Hello

On Friday 08 September 2006 14:51, grossnik.mailinglists@hispeed.ch wrote:
> Hi Vladimir
>
> >please run
> >for i in `cat /root/hda3.bad`; do debugreiserfs -1 $i /dev/hda3 >
> > /dev/null; done
>
> So many Thx for very fast response.
> Here's the output:
>
>
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602176 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602179 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602180 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602181 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602182 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602183 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602185 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602186 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602187 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602188 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602189 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602190 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602191 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602193 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602194 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602195 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602196 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602197 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602198 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602199 is used in ondisk bitmap
> debugreiserfs 3.6.19 (2003 www.namesys.com)
>
> 4602201 is used in ondisk bitmap
>

ok, all bad blocks are used. Lets try to find what they are used for:

get ftp://ftp.namesys.com/pub/tmp/reiserfsprogs-3.6.19.3.tar.gz
and run its debugreiserfs:

cat /root/hda3.bad | debugreiserfs -x /dev/hda3

Re: reiserfsck (3.6.19) --rebuild-tree failed

[Vladimir V. Saveliev]

Hello

On Friday 08 September 2006 15:30, grossnik.mailinglists@hispeed.ch wrote:
> Hi Vladimir
>
> >ok, all bad blocks are used. Lets try to find what they are used for:
> >cat /root/hda3.bad | debugreiserfs -x /dev/hda3
>
> # cat /root/hda3.bad | ./debugreiserfs -x /dev/hda3 > /root/tmp.txt 2>&1
> =>
>
> debugreiserfs 3.6.19.3 (2003 www.namesys.com)
>
> list of 21 block numbers is read
> /0

ah, sorry, I forgot that you ran reiserfsck --rebuild-tree and that did not 
complete. debureiserfs -x will not help.

I will try to reproduce your problem here and debug it.

Btw, did reiserfstune say you something like the below?

reiserfstune -B list2 /dev/hda2
reiserfstune: Bad block 32793 is used already in reiserfs tree. To mark it as 
a bad block use reiserfsck
--fix-fixable with -B option.




> block #0 has wrong level 0, has to be 65534
> Number of unresolved block numbers: 21
>
>
>
> Kind Regards
> Bruno

Re: reiserfsck (3.6.19) --rebuild-tree failed

[Vladimir V. Saveliev]

Hello

On Friday 08 September 2006 16:04, grossnik.mailinglists@hispeed.ch wrote:
> Vladimir
>
> >Btw, did reiserfstune say you something like the below?
> >
> >reiserfstune -B list2 /dev/hda2
> >reiserfstune: Bad block 32793 is used already in reiserfs tree. To mark it
> > as a bad block use reiserfsck
> >--fix-fixable with -B option.
>
> Yes. exactly.
> Then I did:
> reiserfsck --rebuild-tree --badblocks /root/hda3.bad /dev/hda3
>
> after 25% the --rebuild-tree stopped saing that there were bad blocks and
> that I've to provide the -B option and a badblock file. (I thought that -B
> and --badblocks were the same?)

yes

>
> I did not use the --fix-fixable option.
>
please run 
reiserfsck (3.6.19.3) --rebuild-tree --badblocks /root/hda3.bad /dev/hda3 
once again and let me see whole output of the command.

Re: Re: reiserfsck (3.6.19) --rebuild-tree failed

[grossnik.mailinglists]

Hi Vladimir
>please run 
>reiserfsck (3.6.19.3) --rebuild-tree --badblocks /root/hda3.bad /dev/hda3 
>once again and let me see whole output of the command.


I'm 100% happy. Now it did not stop.
Either it would haven been nessesary to run it twice or the new version I've got from did the trick.

I thank you so much!
Now I go any buy a new disk!!!

Here's the output (I deleted not usefull text and marked it with ...)

reiserfsck 3.6.19.3 (2003 www.namesys.com)

*************************************************************
** Do not  run  the  program  with  --rebuild-tree  unless **
** something is broken and MAKE A BACKUP  before using it. **
** If you have bad sectors on a drive  it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive  to the good one -- dd_rescue is  a good tool for **
** that -- and only then run this program.                 **
** If you are using the latest reiserfsprogs and  it fails **
** please  email bug reports to reiserfs-list@namesys.com, **
** providing  as  much  information  as  possible --  your **
** hardware,  kernel,  patches,  settings,  all reiserfsck **
** messages  (including version),  the reiserfsck logfile, **
** check  the  syslog file  for  any  related information. **
** If you would like advice on using this program, support **
** is available  for $25 at  www.namesys.com/support.html. **
*************************************************************

Will rebuild the filesystem (/dev/hda3) tree
Bad block list will contain only blocks specified in '/root/hda3.bad' file
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Replaying journal..
Reiserfs journal '/dev/hda3' in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Fri Sep  8 15:33:05 2006
###########

Pass 0:
Loading on-disk bitmap .. ok, 992967 blocks marked used
Skipping 8360 blocks (super block, journal, bitmaps) 984586 blocks will be read
0%                                                          left 984585, 0 /sec

...

left 26944, 5503 /sec                        left 21343, 5504 /sec
io.c: bread: 471: Cannot read the block (4602192): (Input/output error).
do_pass_0: Reading of the block 4602192 failed
                        left 21321, 4965 /sec
io.c: bread: 471: Cannot read the block (4602200): (Input/output error).
do_pass_0: Reading of the block 4602200 failed
                        left 18822, 4952 /sec                        left 15824, 4942 /sec                        left 12987, 4931 /sec                         left 9920, 4922 /sec                         left 6805, 4913 /sec                         left 1611, 4914 /sec100%                        left 0, 4922 /sec
	"r5" hash is selected
Flushing..finished
	Read blocks (but not data blocks) 984584
		Leaves among those 20634
		Objectids found 90556

Pass 1 (will try to insert 20634 leaves):
Looking for allocable blocks .. finished
0%                                                           left 20633, 0 /sec

...

 left 6518, 1411 /sec..80%                             left 4074, 1505 /sec....100%                        left 0, 1875 /sec
Flushing..finished
	20634 leaves read
		20467 inserted
		167 not inserted

Pass 2:
0%                                                             left 333, 0 /sec                                                             left 332, 0 /sec                                                             left 331, 0 /sec
...

 left 0, 0 /sec
Flushing..finished
	Leaves inserted item by item 167
Pass 3 (semantic):
####### Pass 0 #######
90547 directory entries were hashed with "r5" hash.
####### Pass 1 #######
####### Pass 2 #######
####### Pass 3 #########
/..    /grossnik/..
...
/.saves-14890-kim.voyager.space.xx~ /.saves-6417-kim.localdomain~                                                                /lost+found/..                Flushing..finished
	Files found: 80711
	Directories found: 8677
	Symlinks found: 1153
	Others: 4
Pass 3a (looking for lost dir/files):
Looking for lost directories:
               done 0, 0 /sec               done 1, 0 /sec          done 9483, 225 /secFlushing..finished
Pass 4 -                done 0, 0 /sec
finished
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Fri Sep  8 15:37:33 2006
###########
####### Pass 3a (lost+found pass) #########

Re: reiserfsck (3.6.19) --rebuild-tree failed

[Michael Weissenbacher]

Hi,
 > I'm 100% happy. Now it did not stop.
 > Either it would haven been nessesary to run it twice or the new 
version I've got from did the trick.
Good to hear that!
 > I thank you so much!
 > Now I go any buy a new disk!!!
Usually when a disk goes bad you should get a new disk FIRST, then make 
an image from the old disk with dd_rescue and then use fsck. It is much 
safer this way and you don't have to fiddle around with the badblock 
options at all.

Useful links:
[1] http://www.garloff.de/kurt/linux/ddrescue/
[2] http://www.knopper.net/knoppix/
[3] http://www.extremetech.com/article2/0,1697,1928206,00.asp

kind regards,
Michael