jffs2: mount problems when XATTR is enabled

[Paul Wakeman]

KaiGai Kohei <kaigai at ak.jp.nec.com> wrote:

> Did you pack any xattr in the filesystem image?

No. The initial rootfs has no files with xattrs. Applications add
attributes when the system operates. These errors occur before the
first xattr is written.

> is 0xffffff. In addition, 0x013c (316byte) and 0x07e0 (2016byte) are
> too long, if these are xattr nodes.

I don't think they're xattr nodes. These errors happen on first boot
when there are no xattrs.

> Is it possible to retry it using the kernel with debug messages.
> (See fs/jffs2/debug.h)

Ok. I'll send the log later.

> > Curiously, if I boot an NFS root and then mount the partition
> > manually, the errors do not occur.
> 
> Is it really same kernel, and same partition?

Yes. 

I mount the partition using

mount -t jffs2 /dev/mtdblock2 /mnt/tmp

I can then modify files under /mnt/tmp and then umount without errors.
There is a delay while I think jffs2 writes its clean markers to erased
sectors within the partition. If I boot with root=/dev/mtdblock2, the
errors occur and although the filesystem mounts, ls gives errors.

I'm beginning to think this is a timing issue at boot, perhaps due to a
bug in another driver. I'll investigate that.

Thanks for your reply.

Paul



      ____________________________________________________________________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz