From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] squashfs-tools: upgrade to newer revision from git
Date: Wed, 1 Jul 2015 15:23:00 +0200 [thread overview]
Message-ID: <20150701132300.GI2409@jama> (raw)
In-Reply-To: <1433765628-15931-1-git-send-email-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Mon, Jun 08, 2015 at 02:13:48PM +0200, Martin Jansa wrote:
> * 4.3 release has nasty hard to reproduce bug in LZO compression
> which in few cases results in one of these 2 errors:
> 1) Lseek failure when creating the FS:
> | writer: Lseek on destination failed because Bad file descriptor, offset=0x1f72306
> | FATAL ERROR:Probably out of space on output filesystem
> | Parallel mksquashfs: Using 32 processors
> | Creating 4.0 filesystem on rootfs.squashfs, block size 262144.
> ..
> 2) failing to read the filesystem in runtime, kernel 3.16.0 showing
> errors like this:
> [ 46.720568] SQUASHFS error: lzo decompression failed, data probably corrupt
> [ 46.730003] SQUASHFS error: squashfs_read_data failed to read block 0x1f72305
> [ 46.740076] SQUASHFS error: Unable to read fragment cache entry [1f72305]
> it's fixed in upstream git repo:
> https://github.com/plougher/squashfs-tools/commit/de03266983ceb62e5365aac84fcd3b2fd4d16e6f
> https://github.com/plougher/squashfs-tools/commit/9c1db6d13a51a2e009f0027ef336ce03624eac0d
> the official repo is:
> https://git.kernel.org/cgit/fs/squashfs/squashfs-tools.git
> but author's github is kept in sync so we can use just that
Ping
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-07-01 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 12:13 [PATCH] squashfs-tools: upgrade to newer revision from git Martin Jansa
2015-07-01 13:23 ` Martin Jansa [this message]
2015-07-10 9:38 ` Alexander Kanavin
2015-07-10 11:06 ` Martin Jansa
2015-07-10 11:31 ` Alexander Kanavin
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=20150701132300.GI2409@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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