From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Bruno Prémont" <bonbons@linux-vserver.org>
Cc: phillip@lougher.demon.co.uk, linux-kernel@vger.kernel.org
Subject: Re: SquashFS io errors - zlib_inflate tried to decompress too much data
Date: Sat, 21 Mar 2009 13:11:01 +0100 [thread overview]
Message-ID: <10f740e80903210511n2867e7adl11fda0f4af04b0d2@mail.gmail.com> (raw)
In-Reply-To: <20090321113315.47562aac@neptune.home>
On Sat, Mar 21, 2009 at 11:33, Bruno Prémont <bonbons@linux-vserver.org> wrote:
>
> With 2.6.29-rc7-git5 (x86, 32bit) I get the following errors on assumed
> correct squashfs images (generated with mksquashfs from CVS, dated
> 2009-03-14)
>
> [ 3481.692558] SQUASHFS error: zlib_inflate tried to decompress too much data, expected 8192 bytes. Zlib data probably corrupt
> [ 3481.692571] SQUASHFS error: squashfs_read_data failed to read block 0x29375e0
> [ 3481.692579] SQUASHFS error: Unable to read metadata cache entry [29375e0]
> [ 3481.692586] SQUASHFS error: Unable to read inode 0x6a04a05ed
>
> The same happens on 2.6.28.8 with all squashfs patches from 2.6.29-rc8
> applied to it (x86, 64bit).
A fix for this has entered mainline:
commit 363911d027d1de1c6df79eb3f487f5476b9619f4
Author: Phillip Lougher <phillip@lougher.demon.co.uk>
Date: Thu Mar 12 03:23:48 2009 +0000
Squashfs: Valid filesystems are flagged as bad by the corrupted fs patch
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2009-03-21 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 10:33 Bruno Prémont
2009-03-21 12:11 ` Geert Uytterhoeven [this message]
2009-03-21 12:35 ` Bruno Prémont
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=10f740e80903210511n2867e7adl11fda0f4af04b0d2@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=bonbons@linux-vserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillip@lougher.demon.co.uk \
/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
all inboxes | Powered by JetHome®