From: Tomasz Chmielewski <mangoo@wpkg.org>
To: Chris Mason <chris.mason@oracle.com>,
Tomasz Chmielewski <mangoo@wpkg.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Oops on a converted ext4 system
Date: Tue, 26 May 2009 23:25:18 +0200 [thread overview]
Message-ID: <4A1C5E3E.1040607@wpkg.org> (raw)
In-Reply-To: <4A1BE05E.5040804@wpkg.org>
Tomasz Chmielewski wrote:
> Tomasz Chmielewski wrote:
>
>>>> Pid: 11454, comm: lzop Not tainted (2.6.30-0.rc7.1mdv #1) MS-6728
>>>
>>> Does this kernel have any extra patches in it?
>>
>> It's a distribution kernel with this description: "NOTE: This kernel
>> has no patches and no third-party drivers".
>> So there shouldn't be any extra patches in it.
>
> BTW, mini-904.img.lzo is ~57 GB big; I wanted to uncompress it on the
> same btrfs filesystem with 15 GB left; but it failed immediately.
I rebooted the system and tried once again - after uncompressing about 3
GB, it didn't like the checksums:
# lzop -d mini-904.img.lzo
lzop: mini-904.img.lzo: Checksum error
# dmesg
btrfs no csum found for inode 9874460 start 2604158976
btrfs no csum found for inode 9874460 start 2604163072
btrfs no csum found for inode 9874460 start 2604167168
btrfs no csum found for inode 9874460 start 2604171264
btrfs no csum found for inode 9874460 start 2604175360
btrfs no csum found for inode 9874460 start 2604179456
btrfs no csum found for inode 9874460 start 2604183552
btrfs no csum found for inode 9874460 start 2604187648
btrfs no csum found for inode 9874460 start 2604191744
btrfs no csum found for inode 9874460 start 2604195840
btrfs csum failed ino 9874460 off 2604167168 csum 2329941848 private 0
btrfs csum failed ino 9874460 off 2604163072 csum 318014017 private 0
btrfs csum failed ino 9874460 off 2604158976 csum 414044261 private 0
btrfs csum failed ino 9874460 off 2604195840 csum 3818597601 private 0
btrfs csum failed ino 9874460 off 2604191744 csum 315821168 private 0
btrfs csum failed ino 9874460 off 2604187648 csum 2401592681 private 0
btrfs csum failed ino 9874460 off 2604183552 csum 402930804 private 0
btrfs csum failed ino 9874460 off 2604179456 csum 2710516765 private 0
btrfs csum failed ino 9874460 off 2604175360 csum 3446408033 private 0
btrfs csum failed ino 9874460 off 2604171264 csum 3221630271 private 0
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2009-05-26 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 6:27 Oops on a converted ext4 system Tomasz Chmielewski
2009-05-26 9:14 ` Chris Mason
2009-05-26 9:22 ` Tomasz Chmielewski
2009-05-26 12:28 ` Tomasz Chmielewski
2009-05-26 21:25 ` Tomasz Chmielewski [this message]
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=4A1C5E3E.1040607@wpkg.org \
--to=mangoo@wpkg.org \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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