reiserfs v3.6 problems

reiserfs v3.6 problems

[mack ragan]

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

Hi,

My root partition will not mount...strange problems have built up to this,
like not being able to read files as root...and I get the following output
frim "debugreiserfs /dev/hdb2":

debugreiserfs 3.6.19 (2003 www.namesys.com)


Filesystem state: consistency is not checked after last mounting

Reiserfs super block in block 16 on 0x342 of format 3.6 with standard
journal
Count of blocks on the device: 6359728
Number of bitmaps: 195
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
blocks): 6359728
Root block: 0
Filesystem is clean
Tree height: 0
Hash function used to sort names: "r5"
Objectid map size 968, max 972
Journal parameters:
        Device [0x0]
        Magic [0x482c3fa]
        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: 0x3:
        FATAL corruptions exist.
         some corruptions exist.
sb_version: 2
inode generation number: 49892980
UUID: 3eeff8ac-8c07-4a98-b126-7bcebd4480c1
LABEL:
Set flags in SB:
        ATTRIBUTES CLEAN

I have run "reiserfsck --rebuild-sb" and "reiserfsck --rebuild-tree" based
on some forum/message boards regarding similar symptoms/issues, but still no
good.  Is there anyway I can recover?  I'm not very experienced with
reiserfs, so any help is very appreciated.

Thanks!

[-- Attachment #2: Type: text/html, Size: 1978 bytes --]

Re: reiserfs v3.6 problems

[Edward Shishkin]

mack ragan wrote:
> Hi,
> 
> My root partition will not mount...strange problems have built up to this,
> like not being able to read files as root...and I get the following output
> frim "debugreiserfs /dev/hdb2":
> 
> debugreiserfs 3.6.19 (2003 www.namesys.com)
> 
> 
> Filesystem state: consistency is not checked after last mounting
> 
> Reiserfs super block in block 16 on 0x342 of format 3.6 with standard
> journal
> Count of blocks on the device: 6359728
> Number of bitmaps: 195
> Blocksize: 4096
> Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
> blocks): 6359728
> Root block: 0
> Filesystem is clean
> Tree height: 0
> Hash function used to sort names: "r5"
> Objectid map size 968, max 972
> Journal parameters:
>        Device [0x0]
>        Magic [0x482c3fa]
>        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: 0x3:
>        FATAL corruptions exist.
>         some corruptions exist.
> sb_version: 2
> inode generation number: 49892980
> UUID: 3eeff8ac-8c07-4a98-b126-7bcebd4480c1
> LABEL:
> Set flags in SB:
>        ATTRIBUTES CLEAN
> 
> I have run "reiserfsck --rebuild-sb" and "reiserfsck --rebuild-tree" based
> on some forum/message boards regarding similar symptoms/issues, but 
> still no
> good.  Is there anyway I can recover?  I'm not very experienced with
> reiserfs, so any help is very appreciated.

It would be better at first to have a backup on a bigger spare partition
using dd. Then try reiserfsck --rebuild-tree on the created image and
send the output.

> 
> Thanks!
>