reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <doiggl@velocitynet.com.au>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: Ivan Shapovalov <intelfx100@gmail.com>, reiserfs-devel@vger.kernel.org
Subject: Re: reiser4progs revision.
Date: Fri, 30 Jan 2015 19:03:58 +1100	[thread overview]
Message-ID: <a537b11102c920b87a1d62f66f36bf13@mail.velocitynet.com.au> (raw)
In-Reply-To: <54007FCF.6050500@gmail.com>

On Fri, 29 Aug 2014 15:27:43 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 08/29/2014 04:16 AM, doiggl@velocitynet.com.au wrote:
>>>>> This is a bug in fsck: it jumps to wrong branch for some reasons.
>>>>> Not yet fixed.
>>>>>
>>>>> Edward.

Hello,
Is there any news on the fix to correct [1]
--Glenn

see:
http://www.spinics.net/lists/reiserfs-devel/msg04206.html

[1]
message:

        Looks like the filesystem is damaged. Make sure that reiser4progs
are
        installed
        and run

        # fsck.reiser4 --build-fs /dev/sdb

        (You may need to use --force because apparently you have R4 on a
whole
        disk,
        not on a partition.)

        Hope that helps,

    #

    Hello,
    Thanks for the details.

    I did the fpllowing steps:
    # fsck.reiser4 --build-fs --force  /dev/sdb
    *******************************************************************
    This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
    *******************************************************************

    Fscking the /dev/sdb block device.

    Will check the consistency of the Reiser4 SuperBlock. Will build the
Reiser4 FileSystem. ***** fsck.reiser4 started at Tue Aug 26 17:22:24 2014

    Reiser4 fs was detected on /dev/sdb.

    Master super block (16):

    magic:          ReIsEr4
    blksize:        4096
    format:         0x0 (format40)
    uuid:           3006ced1-7490-4ea8-a9b8-d82143c6bede
    label:          <none>

    Format super block (17):

    plugin:         format40
    description:    Disk-format plugin.
    version:        0
    magic:          ReIsEr40FoRmAt
    mkfs id:        0x1ddaf754
    flushes:        0
    blocks:         488378640
    free blocks:    217146980
    root block:     37017218
    tail policy:    0x2 (smart)
    next oid:       0xedade
    file count:     188313
    tree height:    6
    key policy:     LARGE

    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.

  parent reply	other threads:[~2015-01-30  8:03 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 [this message]
2015-02-11  8:26       ` What can I do next to use R4 partition sdb doiggl
2015-04-13  3:55       ` Can the fix for 'bug in fsck: it jumps to wrong branch for some reason' be included in next reiser4progs please doiggl
2015-12-12  8:45       ` What can I do next to use R4 partition sdb 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=a537b11102c920b87a1d62f66f36bf13@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).