From: <doiggl@velocitynet.com.au>
To: reiserfs-devel@vger.kernel.org
Cc: Edward Shishkin <edward.shishkin@gmail.com>
Subject: reiser4progs and Wrong order of keys. query [on sdb]
Date: Thu, 05 Mar 2015 14:00:40 +1100 [thread overview]
Message-ID: <3ceb7fd89df3e379f7d8b195bd814b11@mail.velocitynet.com.au> (raw)
Hello,
Is there a patch available to fix the problem of [1]
I'm using reiser4progs: version-1.0.9
--Thanks Glenn
I can apply patch and build at:
https://build.opensuse.org/package/view_file/home:doiggl/reiser4progs/reiser4progs.spec?expand=1
- I can make a image copy of disk[using linux dd] to another disk and use
that to see if repair works.
- run # fsck.reiser4 --build-fs --force /dev/sdb
- run # fsck.reiser4 --check /dev/sdb
- see if volume can be accessed:
mount command used.
mount /dev/sdb /media/disk
- I can report results back to list.
Background history
==================
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
http://www.spinics.net/lists/reiserfs-devel/msg04682.html
[1]
fsck.reiser4 --build-fs --force /dev/sdb
.
.
LOOKING FOR UNCONNECTED NODES FSCK: node.c: 108:
repair_node_items_check: Node (43828275), items (0)
and
(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
reply other threads:[~2015-03-05 3:00 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=3ceb7fd89df3e379f7d8b195bd814b11@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=edward.shishkin@gmail.com \
--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).