From: Pat Double <pat@patdouble.com>
To: reiserfs-list@namesys.com
Subject: Reiser4 corruption with 2.6.12.1
Date: Fri, 24 Jun 2005 13:46:09 -0500 [thread overview]
Message-ID: <200506241346.09072.pat@patdouble.com> (raw)
This may be an unsupported setup, but I am experiencing reproducable errors
with reiser4 on 2.6.12.1. I used the 2.6.12-rc5-mm2 patch set (broken.out.2)
against a vanilla 2.6.12.1 kernel. I did not get any patch failures but a few
offsets. I get errors whenever I add or remove a file in the root directory.
Inside other directories seems to be fine according to fsck.
It is easy to reproduce:
1. mkfs.reiser4 -y /dev/ram1
2. mount -t reiser4 /dev/ram1 /mnt
3. cp <some file> /mnt
4. umount /mnt
5. fsck.reiser4 -y /dev/ram1
CHECKING STORAGE TREE
FSCK: Node (24), item (0), [29:1(SD):0:2a:0]: does not look like a valid SD
plugin set extention: wrong pset member
count detected (12).
FSCK: Node (24), item (0), [29:1(SD):0:2a:0]: does not look like a valid stat
data.
FSCK: Node (24), item (0), [29:1(SD):0:2a:0]: broken item found.
FSCK: Node (24): the node is broken. Pointed from the node (25), item (0),
unit (0). The whole subtree is skipped.
Read nodes 2
Nodes left in the tree 1
Leaves of them 0, Twigs of them 1
Broken of them 1
Leaves of them 1, Twigs of them 0
Time interval: Fri Jun 24 13:44:15 2005 - Fri Jun 24 13:44:15 2005
CHECKING EXTENT REGIONS.
Read twigs 1
Time interval: Fri Jun 24 13:44:15 2005 - Fri Jun 24 13:44:15 2005
Warn : Fatal corruptions were found. Semantic pass is skipped.
***** fsck.reiser4 finished at Fri Jun 24 13:44:15 2005
Closing fs...done
Running with --build-fs will fix the problem. If I create a directory, fix it
with fsck --build-fs, then copy files into the directory I do not get errors.
I'm expecting to hear I should wait for the 2.6.12.1 patches or use the -mm
kernel, but checking nonetheless.
Thanks.
--
Pat Double, pat@patdouble.com
"In the beginning God created the heaven and the earth."
reply other threads:[~2005-06-24 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506241346.09072.pat@patdouble.com \
--to=pat@patdouble.com \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.