Corrupt reiser3 fs

Corrupt reiser3 fs

[Paul Gear]

[-- Attachment #1: Type: text/plain, Size: 3055 bytes --]

Hi folks,

After filling my reiserfs with backups, i ended up with a corrupt
filesystem.  I'm running Debian 3.1 (sarge), kernel 2.6.8-2-k7, and
reiserfsprogs 3.6.19-1.

I don't care about this filesystem and will just recreate it, but i
thought i'd offer folks the opportunity to debug before i trash it.

Here's my fsck output with all the noise cut out:

---------8<----------------------------------------

enoch:/tmp # fsck.reiserfs --rebuild-tree /dev/hdc1
...
111392 directory entries were hashed with "r5" hash.
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 19333032
                Leaves among those 32365
                        - corrected leaves 35
                        - leaves all contents of which could not be
saved and deleted 5
                pointers in indirect items to wrong area 25647 (zeroed)
                Objectids found 104921

Pass 1 (will try to insert 32360 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%....20%....40%....60%...                                  left 8239,
234 /sec
The problem has occurred looks like a hardware problem (perhaps
memory). Send us the bug report only if the second run dies at
the same place with the same block number.

build_the_tree: Nothing but leaves are expected. Block 10905053 - unknown

Aborted

---------8<----------------------------------------

Kernel messages reported during this fsck are as follows:

---------8<----------------------------------------

ReiserFS: hdc1: found reiserfs format "3.6" with standard journal
ReiserFS: hdc1: using ordered data mode
ReiserFS: hdc1: journal params: device hdc1, size 8192, journal first
block 18, max trans len 1024, max batch 900, max commit age 30, max
trans age 30
ReiserFS: hdc1: checking transaction log (hdc1)
ReiserFS: warning: is_tree_node: node level 0 does not match to the
expected one 65534
ReiserFS: hdc1: warning: vs-5150: search_by_key: invalid format found in
block 0. Fsck?
ReiserFS: hdc1: warning: vs-13070: reiserfs_read_locked_inode: i/o
failure occurred trying to find stat data of [1 2 0x0 SD]
ReiserFS: hdc1: Using r5 hash to sort names
ReiserFS: warning: is_tree_node: node level 0 does not match to the
expected one 65534
ReiserFS: hdc1: warning: vs-5150: search_by_key: invalid format found in
block 0. Fsck?
ReiserFS: hdc1: warning: vs-2140: finish_unfinished: search_by_key
returned -2

---------8<----------------------------------------

There is no problem with memory (my other two hard disks and all of my
desktop programs are working fine), or, to my knowledge, the hard disk
or cable (since i can do a full dd of the hard disk to /dev/null).

Anyone interested in taking a look at it, or should i just write it off
as stray gamma rays from Saturn and trash it?  :-)

-- 
Paul
<http://paulgear.webhop.net>
--
Did you know?  Microsoft Internet Explorer and Outlook have a poor track
record for security <http://www.kb.cert.org/vuls/id/713878>.  Why not
try one of the more secure alternatives from <http://mozilla.org>?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

Re: Corrupt reiser3 fs

[evilninja]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Gear schrieb:
> The problem has occurred looks like a hardware problem (perhaps
> memory). Send us the bug report only if the second run dies at
> the same place with the same block number.

so....does it? is it reproduceable on a 2nd run? also with a different
(maybe vanilla) kernel?

before trashing the fs, you could do

  debugreiserfs -p /dev/HDD | bzip2 -c > HDD-meta.bz2

then some reiserfs-guru could use it for debugging.

- --
BOFH excuse #316:

Elves on strike. (Why do they call EMAG Elf Magic)

- --
BOFH excuse #316:

Elves on strike. (Why do they call EMAG Elf Magic)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCrHJkC/PVm5+NVoYRAms/AKC3Nhrq8iRUxjU+PQzI9IXpGVtNOgCfcZ0F
gQBaoD9ga8lKfr1qgB24T7U=
=V18Z
-----END PGP SIGNATURE-----

Re: Corrupt reiser3 fs

[Vitaly Fertman]

On Sunday 12 June 2005 02:42, Paul Gear wrote:
> Hi folks,
> 
> After filling my reiserfs with backups, i ended up with a corrupt
> filesystem.  I'm running Debian 3.1 (sarge), kernel 2.6.8-2-k7, and
> reiserfsprogs 3.6.19-1.
> 
> I don't care about this filesystem and will just recreate it, but i
> thought i'd offer folks the opportunity to debug before i trash it.
> 
> Here's my fsck output with all the noise cut out:
> 
> ---------8<----------------------------------------
> 
> enoch:/tmp # fsck.reiserfs --rebuild-tree /dev/hdc1
> ...
> 111392 directory entries were hashed with "r5" hash.
>         "r5" hash is selected
> Flushing..finished
>         Read blocks (but not data blocks) 19333032
>                 Leaves among those 32365
>                         - corrected leaves 35
>                         - leaves all contents of which could not be
> saved and deleted 5
>                 pointers in indirect items to wrong area 25647 (zeroed)
>                 Objectids found 104921
> 
> Pass 1 (will try to insert 32360 leaves):
> ####### Pass 1 #######
> Looking for allocable blocks .. finished
> 0%....20%....40%....60%...                                  left 8239,
> 234 /sec
> The problem has occurred looks like a hardware problem (perhaps
> memory). Send us the bug report only if the second run dies at
> the same place with the same block number.
> 
> build_the_tree: Nothing but leaves are expected. Block 10905053 - unknown

does it stop every time on the block 10905053 ?
 
> 
> There is no problem with memory (my other two hard disks and all of my
> desktop programs are working fine), or, to my knowledge, the hard disk
> or cable (since i can do a full dd of the hard disk to /dev/null).
> 
> Anyone interested in taking a look at it, or should i just write it off
> as stray gamma rays from Saturn and trash it?  :-)
> 

-- 
Thanks,
Vitaly Fertman

Re: Corrupt reiser3 fs

[Hans Reiser]

Vitaly Fertman wrote:

>On Sunday 12 June 2005 02:42, Paul Gear wrote:
>  
>
>>Hi folks,
>>
>>After filling my reiserfs with backups, i ended up with a corrupt
>>filesystem.  I'm running Debian 3.1 (sarge), kernel 2.6.8-2-k7, and
>>reiserfsprogs 3.6.19-1.
>>
>>I don't care about this filesystem and will just recreate it, but i
>>thought i'd offer folks the opportunity to debug before i trash it.
>>
>>Here's my fsck output with all the noise cut out:
>>
>>---------8<----------------------------------------
>>
>>enoch:/tmp # fsck.reiserfs --rebuild-tree /dev/hdc1
>>...
>>111392 directory entries were hashed with "r5" hash.
>>        "r5" hash is selected
>>Flushing..finished
>>        Read blocks (but not data blocks) 19333032
>>                Leaves among those 32365
>>                        - corrected leaves 35
>>                        - leaves all contents of which could not be
>>saved and deleted 5
>>                pointers in indirect items to wrong area 25647 (zeroed)
>>                Objectids found 104921
>>
>>Pass 1 (will try to insert 32360 leaves):
>>####### Pass 1 #######
>>Looking for allocable blocks .. finished
>>0%....20%....40%....60%...                                  left 8239,
>>234 /sec
>>The problem has occurred looks like a hardware problem (perhaps
>>memory). Send us the bug report only if the second run dies at
>>the same place with the same block number.
>>
>>build_the_tree: Nothing but leaves are expected. Block 10905053 - unknown
>>    
>>
Please improve this error message if you can.

>
>does it stop every time on the block 10905053 ?
> 
>  
>
>>There is no problem with memory (my other two hard disks and all of my
>>desktop programs are working fine), or, to my knowledge, the hard disk
>>or cable (since i can do a full dd of the hard disk to /dev/null).
>>
>>Anyone interested in taking a look at it, or should i just write it off
>>as stray gamma rays from Saturn and trash it?  :-)
>>
>>    
>>
>
>  
>