From: "Paul Wakeman" <prwakeman@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: jffs2: mount problems when XATTR is enabled
Date: Tue, 24 Jul 2007 12:59:37 +0100 [thread overview]
Message-ID: <2f9409cb0707240459m9def03cy775b3f4dcf36b39b@mail.gmail.com> (raw)
I'm seeing lots of jffs2 errors at boot when mounting filesystems. My
kernel has XATTR enabled. If I build my kernel without
CONFIG_JFFS2_FS_XATTR, the errors don't occur. What are the
requirements for a working jffs2 with XATTR? Are there dependencies of
userspace utilities - mount, mkfs.jffs2 etc?
Errors are of the form:-
Node totlen on flash (0xffffffff) != totlen from node ref (0x0000013c)
at 0x00322d24
Node totlen on flash (0xffffffff) != totlen from node ref (0x000007e0)
at 0x00322544
The filesystem mounts but "ls" gives errors:
# ls /
ls: Input/output error
My board has NOR and NAND flash. The errors occur in NOR partitions.
System info:-
Freescale MX31 CPU (ARM11 core)
2.6.19 kernel
mkfs.jffs2 version 1.50
gcc 4.1.1 (glibc)
busybox 1.1.3
I tried patching my kernel with the MTD code from the latest 2.6.22
kernel but it results in the same problems. I also tried the latest
mkfs.jffs2 from git (which reports the same version number though I
don't think it is...).
Curiously, if I boot an NFS root and then mount the partition
manually, the errors do not occur.
Any ideas?
Thanks
Paul
next reply other threads:[~2007-07-24 11:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:59 Paul Wakeman [this message]
2007-07-25 2:31 ` jffs2: mount problems when XATTR is enabled KaiGai Kohei
2007-07-25 8:42 ` Paul Wakeman
2007-07-25 9:39 ` KaiGai Kohei
2007-07-25 11:04 ` Paul Wakeman
2007-07-26 2:42 ` KaiGai Kohei
2007-07-26 3:46 ` KaiGai Kohei
2007-07-26 14:44 ` Paul Wakeman
2007-07-30 4:42 ` KaiGai Kohei
2007-07-26 11:39 ` Paul Wakeman
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=2f9409cb0707240459m9def03cy775b3f4dcf36b39b@mail.gmail.com \
--to=prwakeman@yahoo.com \
--cc=linux-mtd@lists.infradead.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