From: Edward Shishkin <edward.shishkin@gmail.com>
To: Gleb Baryshev <gleb.baryshev@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: fsck.reiser4 (libaal-1.0.5) segfault
Date: Thu, 03 Feb 2011 20:09:22 +0100 [thread overview]
Message-ID: <4D4AFD62.9040507@gmail.com> (raw)
In-Reply-To: <4D4AF4AA.9000302@gmail.com>
Gleb Baryshev wrote:
> 03.02.2011 14:33, Edward Shishkin writes:
>> Hello.
>>
>> Could you please pack the metadata by
>> debugfs.reiser4 -P /dev/xxx | gzip > meta.gz
>> and let me download the file meta.gz
>
> Here's link to bzipped metadata:
> http://tootiny.net/zq09qj
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
>
>> This kind of corruption might indicate bugs
>> in reiser4 kernel stuff. In what circumstances
>> did it happen (was it power loss, etc), and
>> what kernel did you use?
>
> There was a hard reset with reiser4 partition mounted, because kernel
> was hung due to oops:
reiser4-for-2.6.35 is buggy, please consider upgrading to .36 or later..
Edward.
>
>
> Feb 3 06:04:13 main20b kernel: BUG: unable to handle kernel paging
> request at 4b1b5d0b
> Feb 3 06:04:13 main20b kernel: IP: [<c11234e1>]
> jbd2_journal_start+0x2a/0xaf
> Feb 3 06:04:13 main20b kernel: *pde = 00000000
> Feb 3 06:04:13 main20b kernel: Oops: 0000 [#1]
> Feb 3 06:04:13 main20b kernel: last sysfs file:
> /sys/devices/pci0000:00/0000:00:1f.5/host0/target0:0:0/0:0:0:0/block/sda/removable
>
> Feb 3 06:04:13 main20b kernel: Modules linked in: reiser4
> lzo_compress zlib_deflate nls_cp866 vfat fat vboxnetadp vboxnetflt
> vboxdrv ext2 xfs exportfs reiserfs floppy processor thermal button atl1
>
>
> Kernel is 2.6.35 - vanilla, patched with corresponding release of
> Reiser4 (thus, reiser4 module isn't the latest).
>
> Regards,
> Gleb
> --
> To unsubscribe from this list: send the line "unsubscribe
> reiserfs-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-02-03 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 8:20 fsck.reiser4 (libaal-1.0.5) segfault Gleb Baryshev
2011-02-03 11:33 ` Edward Shishkin
2011-02-03 18:32 ` Gleb Baryshev
2011-02-03 19:09 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-03 21:05 Gleb Baryshev
2011-02-03 22:09 ` Edward Shishkin
2011-02-06 22:28 ` Edward Shishkin
2011-02-07 9:21 ` Gleb Baryshev
2011-02-07 10:27 ` 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=4D4AFD62.9040507@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=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).