Re: jffs2: mount problems when XATTR is enabled

[KaiGai Kohei <kaigai@ak.jp.nec.com>]

Paul,

 >> 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.

I wonder why jffs2/xattr code gave an effect your flash device
without any xattr node, because any xattr related implementation
is invoked only when jffs2 found xattr nodes on the medium, or
xattr related operations are done (like setfacl).

>> Is it possible to retry it using the kernel with debug messages.
>> (See fs/jffs2/debug.h)
> 
> Ok. I'll send the log later.

I think Kconfig related to JFFS2 also helps us to understand the situation.

 > 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.

What's happen when you boot the board with NFS root, and mount the errored
partition manually again?
If you can reproduce the error, I recommend you to try the same test
on mtdram pseudo mtd device next.

-- 
Open Source Software Promotion Center, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>