From: Gleb Baryshev <gleb.baryshev@gmail.com>
To: reiserfs-devel@vger.kernel.org
Subject: Re: fsck.reiser4 (libaal-1.0.5) segfault
Date: Fri, 04 Feb 2011 00:05:11 +0300 [thread overview]
Message-ID: <4D4B1887.3020306@gmail.com> (raw)
03.02.2011 22:09, Edward Shishkin writes:
> Sorry, but this file looks corrupted.
> Could you please try again?
>
> Also make sure that packed meta-data are
> extracted correctly by the following way:
>
> #touch meta_tmp
> #bzcat meta.bz2 | debugfs.reiser4 -U meta_tmp
For some reason, debugfs was adding junk every time - 8 bytes (1B 5B 3F
31 30 33 34 68) before 'VRSN'; in other respects the metadata file is
all right. Finally I ran debugfs from LiveCD and got correct dump:
http://tootiny.net/813h25
BTW, fsck from LiveCD segfaulted, too.
Gleb
next reply other threads:[~2011-02-03 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 21:05 Gleb Baryshev [this message]
2011-02-03 22:09 ` fsck.reiser4 (libaal-1.0.5) segfault Edward Shishkin
2011-02-06 22:28 ` Edward Shishkin
2011-02-07 9:21 ` Gleb Baryshev
2011-02-07 10:27 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 8:20 Gleb Baryshev
2011-02-03 11:33 ` Edward Shishkin
2011-02-03 18:32 ` Gleb Baryshev
2011-02-03 19:09 ` Edward Shishkin
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=4D4B1887.3020306@gmail.com \
--to=gleb.baryshev@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).