From: <doiggl@velocitynet.com.au>
To: ReiserFS Development List <reiserfs-devel@vger.kernel.org>
Subject: Can I shrink reiser4 volume with gparted gparted-live-0.24.0-2-amd64.iso [/dev/sdb]
Date: Fri, 04 Dec 2015 13:18:22 +1100 [thread overview]
Message-ID: <f6902d30f9d22c79fad056e47c553eb8@mail.velocitynet.com.au> (raw)
Question.
Can I shrink reiser4 volume with gparted gparted-live-0.24.0-2-amd64.iso
[/dev/sdb]
r4 metadata has errors as follows [1]:
--Glenn
http://gparted.sourceforge.net/download.php
[1]
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
CHECKING THE STORAGE TREE Read nodes 197008413 Nodes left in the tree
197008413 Leaves of them 194764277, Twigs of them 2217790 Time interval:
Tue Aug 26 17:24:21 2014 - Wed Aug 27 01:25:31 2014 CHECKING EXTENT
REGIONS. Read twigs 2217790 Time interval: Wed Aug 27 01:25:31 2014 - Wed
Aug 27 03:35:39 2014 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
FS is consistent.
This is a bug in fsck: it jumps to wrong branch for some reasons.
Not yet fixed.
Edward.
--
reply other threads:[~2015-12-04 2:18 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=f6902d30f9d22c79fad056e47c553eb8@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).