From: Dick Hollenbeck <dick@softplc.com>
To: linux-kernel@vger.kernel.org
Subject: SquashFS on ARM9
Date: Sat, 06 Feb 2010 18:55:36 -0600 [thread overview]
Message-ID: <4B6E0F88.2020402@softplc.com> (raw)
Dear Philip et. al,
I am using 2.6.30.5 on an ARM9 with squashfs.
The squashFS image is built with x86_64 form of
mksquashfs version 4.1-CVS (2009/09/20)
a 64 bit linux program.
The image mounts into the 64 bit development system OK and I can read a
particular file. There are no problems on the development system, only
the ARM9.
When mounted on ARM9 with said kernel, I get a read error reading that
same particular file:
dmesg:
SQUASHFS error: zlib_inflate error, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x50581
SQUASHFS error: Unable to read fragment cache entry [50581]
SQUASHFS error: Unable to read page, block 50581, size b6f3
SQUASHFS error: Unable to read fragment cache entry [50581]
SQUASHFS error: Unable to read page, block 50581, size b6f3
SQUASHFS error: Unable to read fragment cache entry [50581]
SQUASHFS error: Unable to read page, block 50581, size b6f3
That image resides on a CF card mounted with loop on the target ARM9.
If I unmount the image, I can SSH copy it out off the flash back to the
development system and do a binary compare on it there against the
original and it is not corrupted. Remember that the orginal mounts fine
on the development system. I think this means that the CF card is not
corrupted.
Am I running into an alignment bug on the ARM9 or an endianess issue?
(ARM9 is lsbyte first as far as I thought, same as the x86_64 Ubuntu
Karmic development system.)
I checked the squashfs kernel block.c file against the latest mainline
and they agree.
Please offer help.
Thanks,
Dick
next reply other threads:[~2010-02-07 1:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 0:55 Dick Hollenbeck [this message]
2010-02-07 7:18 ` SquashFS on ARM9 Dick Hollenbeck
2010-02-07 13:52 ` Phillip Lougher
2010-02-07 15:10 ` Dick Hollenbeck
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=4B6E0F88.2020402@softplc.com \
--to=dick@softplc.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.