From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Subject: A request for fix for 'FSCK: node.c: Wrong order of keys.'
Date: Wed, 14 Oct 2015 10:49:15 +1100 [thread overview]
Message-ID: <fa254638aecdadfc37c99129b79e46e5@mail.velocitynet.com.au> (raw)
In-Reply-To: <02dbaf91d2fcee90ee2f08ec0c937a63@mail.velocitynet.com.au>
Hello,
A request for fix for 'FSCK: node.c: Wrong order of keys.'
Can problem be fixed ?
Thanks
--Glenn
# fsck.reiser4 -V
fsck.reiser4 1.1.0
Format release: 4.0.1
# rpm -qa |grep -i reiser4 |sort
kernel-reiser4-4.1.6-7.1.gd2bbe7f.x86_64
libreiser4-1_1-0-1.1.0-14.1.x86_64
reiser4progs-1.1.0-14.1.x86_64
# full spec file:
https://build.opensuse.org/package/view_file/home:doiggl/reiser4progs/reiser4progs.spec?expand=1
Background history
==================
http://www.spinics.net/lists/reiserfs-devel/msg04727.html
[from url]
#fsck.reiser4 --build-fs --force /dev/sdb
.
.
LOOKING FOR UNCONNECTED NODES
#http://www.spinics.net/lists/reiserfs-devel/msg04206.html
# fsck.reiser4 --build-fs --force /dev/sdb
.
.
(1): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (52697435), items (79)
and (80): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (63227569), items (24)
and (25): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (63227571), items (73)
and (74): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (116595727), items
(20)
and (21): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (227923161), items
(22)
and (23): Wrong order of keys.
FSCK: node.c: 108: repair_node_items_check: Node (284305753), items
(61)
and (62): Wrong order of keys.
Read nodes 1481038
Good nodes 471512
Leaves of them 466164, Twigs of them 5348
Time interval: Wed Aug 27 03:35:57 2014 - Wed Aug 27 03:39:46
2014
***** fsck.reiser4 finished at Wed Aug 27 03:39:46 2014
Closing fs...done
FS is consistent.
parent reply other threads:[~2015-10-13 23:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <02dbaf91d2fcee90ee2f08ec0c937a63@mail.velocitynet.com.au>]
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=fa254638aecdadfc37c99129b79e46e5@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).