Package: reiser4progs
Version: 1.0.7-5

I have my /home on reiser4 with compression.
I use zen project kernels, which have reiser4 support.
The current is 2.6.32-zen2
I have problems with this partition, so I've run fsck.reiser4. Here is
the output:


valentine-pc:/home/valentine# fsck.reiser4 /dev/mapper/isw_jfcfihbei_RAID08
*******************************************************************
This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
*******************************************************************

Fscking the /dev/mapper/isw_jfcfihbei_RAID08 block device.
Will check the consistency of the Reiser4 SuperBlock.
Will check the consistency of the Reiser4 FileSystem.
Continue?
(Yes/No): Yes
***** fsck.reiser4 started at Tue Dec 22 16:58:57 2009
Reiser4 fs was detected on /dev/mapper/isw_jfcfihbei_RAID08.
Master super block (16):
magic:          ReIsEr4
blksize:        4096
format:         0x0 (format40)
uuid:           <none>
label:          <none>

Format super block (17):
plugin:         format40
description:    Disk-format plugin.
version:        0
magic:          ReIsEr40FoRmAt
mkfs id:        0x5ef41903
flushes:        0
blocks:         7323616
free blocks:    4932387
root block:     7235172
tail policy:    0x2 (smart)
next oid:       0x6564fc
file count:     294497
tree height:    5
key policy:     LARGE


CHECKING THE STORAGE TREE
        Read nodes 918358
        Nodes left in the tree 918358
                Leaves of them 906695, Twigs of them 11479
        Time interval: Tue Dec 22 16:59:00 2009 - Tue Dec 22 17:00:48 2009
CHECKING EXTENT REGIONS.
        Read twigs 11479
        Time interval: Tue Dec 22 17:00:48 2009 - Tue Dec 22 17:01:16 2009
CHECKING THE SEMANTIC TREE
FSCK: /tmp/buildd/reiser4progs-1.0.7/plugin/object/ccreg40/ccreg40_repair.c:
77: ccreg40_check_item: The file [52cf8a:62756874753465:5ce9cc]
(ccreg40), node [7252143], item [1]:
item of the wrong cluster size (-2147483648) found, Should be (65536).
Segmentation fault

The visible problem in fs is that there are files that cause processes
reading them to hang (they can be killed only by magic SysRqs).
I had similar problems before, and the segfaults stopped when I
removed failing files. But now I don't know where the buggy files are.

--
Best regards,
Valentin Pavlyuchenko



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to