From: <doiggl@velocitynet.com.au>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please.
Date: Mon, 13 Apr 2015 13:55:26 +1000 [thread overview]
Message-ID: <fe825cd2109d17b1c9fb593ef3ecc8fa@mail.velocitynet.com.au> (raw)
In-Reply-To: <53FDD565.6030500@gmail.com>
Hello,
Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be
included in next reiser4progs please.
Thank you.
--Glenn
references and history:
http://www.spinics.net/lists/reiserfs-devel/msg04206.html
http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/
reiser4progs-1.0.9.tar.gz 2014-06-29 913.5 kB
http://sourceforge.net/projects/reiser4/files/reiser4-utils/reiser4progs/reiser4progs-1.0.9.tar.gz
# cat ./ChangeLog
This file is part of reiser4progs package
Copyright (C) 2001, 2002, 2003, 2004 by Hans Reiser, licensing governed by
reiser4progs/COPYING.
This file may be modified and/or distributed without restriction. This is
not an invitation to misrepresent the history of reiser4progs.
2014-06-28
1.0.9 version
2014-06-28
discard option to mkfs -- discard device at filesystem creation
time (for SSD drives)
Fixup in librepair/twig_scan.c: cb_item_region_check().
2013-05-03
1.0.8 version
.
.
.
#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.
>
>
> This is a bug in fsck: it jumps to wrong branch for some reasons.
> Not yet fixed.
>
> Edward.
next prev parent reply other threads:[~2015-04-13 3:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 6:52 What can I do next to use R4 partition sdb doiggl
2014-08-26 7:03 ` Ivan Shapovalov
2014-08-27 7:33 ` doiggl
2014-08-27 12:56 ` Edward Shishkin
2014-08-28 2:34 ` reiser4progs revision doiggl
2014-08-28 12:54 ` Edward Shishkin
2014-08-28 14:46 ` dimas
2014-08-29 2:16 ` doiggl
2014-08-29 13:27 ` Edward Shishkin
2014-08-29 14:00 ` doiggl
2015-01-30 8:03 ` doiggl
2015-02-11 8:26 ` What can I do next to use R4 partition sdb doiggl
2015-04-13 3:55 ` doiggl [this message]
2015-12-12 8:45 ` doiggl
2015-02-23 13:41 ` doiggl
2015-02-24 0:00 ` doiggl
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=fe825cd2109d17b1c9fb593ef3ecc8fa@mail.velocitynet.com.au \
--to=doiggl@velocitynet.com.au \
--cc=edward.shishkin@gmail.com \
--cc=intelfx100@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).