From: <doiggl@velocitynet.com.au>
To: Edward Shishkin <edward.shishkin@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: ls: reading directory .: Input/output error on reiser4 partition
Date: Tue, 12 Apr 2011 22:37:22 +1000 [thread overview]
Message-ID: <3902b176fc930c92f7de292ffced6760@mail.velocitynet.com.au> (raw)
In-Reply-To: <4DA322AF.4050004@gmail.com>
On Mon, 11 Apr 2011 17:47:59 +0200, Edward Shishkin
<edward.shishkin@gmail.com> wrote:
> On 04/11/2011 05:32 PM, doiggl@velocitynet.com.au wrote:
>> On Mon, 11 Apr 2011 15:57:23 +0200, Edward Shishkin
>> <edward.shishkin@gmail.com> wrote:
>>> On 04/11/2011 03:50 PM, doiggl@velocitynet.com.au wrote:
>>>> Hello
>>>> I get this error on a Reiser4 disk:
>>>>
>>>> What are the commands to
>>>> - check disk structure
>>>
>>>
>>> make sure /dev/sdd is unmounted, or mounted read-only;
>>> fsck.reiser4 /dev/sdd
>>>
>>>
>>>> - list any errors
>>>> - repair errors
>>>>
>>>> I am using Reiser4 vers 2.6.38
>>>> Build log
>>>>
>>
->https://build.opensuse.org/package/binaries?package=kernel-reiser4&project=home%3Adoiggl&repository=openSUSE_11.4
>>>>
>>
>> Hello
>> Thanks for the info
>> I did the following
>> - installed reiser4progs
>> - umount /dev/sdd
>>
>> This next step will take a long time [in progress] Its at 0%
>> -I'll reply later with full result, its checking 1.2 TB data and>
>> 250,000
>> files
>
>
> Reiser4 doesn't have production stability so far,
> so, creating large reiser4 volumes is not a good idea.
>
> An old nasty bug still lives in reiser4 kernel module
> (appearing objects with inconsistent key order).
> Fsck will cope with this kind of corruption, however,
> it will take a lot of time.
>
> Thanks,
> Edward.
>
>> What I have so far.
>> Glenn
>>
>> # fsck.reiser4 /dev/sdd
>> *******************************************************************
>> This is an EXPERIMENTAL version of fsck.reiser4. Read README first.
>> *******************************************************************
>> ***** fsck.reiser4 started at Tue Apr 12 01:18:23 2011
>> Reiser4 fs was detected on /dev/sdd.
>>
>>
>> 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: 184741937
>> root block: 240062537
>> tail policy: 0x2 (smart)
>> next oid: 0xe6e2d
>> file count: 254746
>> tree height: 6
>> key policy: LARGE
>>
>>
>> CHECKING THE STORAGE TREE 0%
>> FSCK: node.c: 108: repair_node_items_check: Node (7616539), items (6)
and
>> (7): Wrong order of keys.
>>
>> FSCK: filter.c: 407: repair_filter_update_traverse: Node (7616539): the
>> node is broken. Pointed from the node (35239054), item (12), unit (0).
>> The whole subtree is skipped.
Hello
Can a single directory be repaired or has the whole disk structure be
repaired in one pass ?
What is the command to repair disk structure.
Thanks
next prev parent reply other threads:[~2011-04-12 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 13:50 ls: reading directory .: Input/output error on reiser4 partition doiggl
2011-04-11 13:57 ` Edward Shishkin
2011-04-11 15:32 ` doiggl
2011-04-11 15:47 ` Edward Shishkin
2011-04-12 12:37 ` doiggl [this message]
2011-04-12 17:18 ` Edward Shishkin
2011-04-13 0:22 ` 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=3902b176fc930c92f7de292ffced6760@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).