From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: Geert Uytterhoeven <geert@linux-m68k.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:35:50 +0100 [thread overview]
Message-ID: <20090321133550.7aa939d2@neptune.home> (raw)
In-Reply-To: <10f740e80903210511n2867e7adl11fda0f4af04b0d2@mail.gmail.com>
Thanks Geert,
I saw that patch but somehow it slipped through when applying the
set of squashfs patches for my 2.6.28.8 install...
With that patch applied access to the image works as expected
Sorry for the noise,
Bruno
On Sat, 21 March 2009 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> 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
prev parent reply other threads:[~2009-03-21 12:36 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
2009-03-21 12:35 ` Bruno Prémont [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=20090321133550.7aa939d2@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=geert@linux-m68k.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®