Marti Raudsepp wrote:
Hi,
Forgot to Cc: the mailing list (I'm new to mailing lists), and also
forgot to mention that I'm on AMD64. The reiser4 file system lives on
a contiguous LVM2 volume.
Regards,
Marti Raudsepp
---------- Forwarded message ----------
From: Marti Raudsepp <marti@xxxxxxxxx>
Date: Jul 11, 2007 3:54 PM
Subject: Re: Undeletable directory in reiser4
To: Edward Shishkin <edward@xxxxxxxxxxx>
On 7/11/07, Edward Shishkin <edward@xxxxxxxxxxx> wrote:
any ideas about kernel version that generated such
inconsistency? It seems this is an old bug..
Oops, sorry, I knew I forgot something important in my rushed bug report.
I'm currently running kernel 2.6.21-gentoo-r3 with the appropriate
reiser4-for-2.6.21 patch. At the time the directory was created, I was
running 2.6.21-ck2.
Would you please pack metadata by
debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
and let me download the file meta.gz
Thanks,
Edward.
Please, check your partition by fsck.reiser4.
Here's what I got:
CHECKING THE SEMANTIC TREE
FSCK: obj40_repair.c: 223: obj40_stat_unix_check: Node (515), item (19),
[41aac:6c6f63616c6500:41aad] (stat40): wrong bytes (182), Should be
(100).
FSCK: obj40_repair.c: 350: obj40_stat_lw_check: Node (515), item (19),
[41aac:6c6f63616c6500:41aad] (stat40): wrong size (3), Should be (2).
Found 86670 objects (some could be encountered more then once).
Time interval: Wed Jul 11 15:41:47 2007 - Wed Jul 11 15:42:00 2007
FSCK: repair.c: 550: repair_sem_fini: On-disk used block bitmap and
really used block bitmap
differ.
***** fsck.reiser4 finished at Wed Jul 11 15:42:00 2007
Closing fs...done
1 fatal corruptions were detected in FileSystem. Run with --build-fs
option to fix them.
I'll leave the file system in the broken state for now.
Regards,
Marti Raudsepp
-
To unsubscribe from this list: send the line "unsubscribe
reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
