JFFS2 corruption when mounting filesystem with filenames oflength > 7

[Steve Deiters]

> -----Original Message-----
> From: linux-mtd-bounces at lists.infradead.org 
> [mailto:linux-mtd-bounces at lists.infradead.org] On Behalf Of 
> Steve Deiters
> Sent: Wednesday, June 23, 2010 5:42 PM
> To: linux-mtd at lists.infradead.org
> Subject: RE: JFFS2 corruption when mounting filesystem with 
> filenames oflength > 7
> 
> > -----Original Message-----
> > From: linux-mtd-bounces at lists.infradead.org
> > [mailto:linux-mtd-bounces at lists.infradead.org] On Behalf Of Steve 
> > Deiters
> > Sent: Wednesday, June 23, 2010 5:21 PM
> > To: linux-mtd at lists.infradead.org
> > Subject: JFFS2 corruption when mounting filesystem with 
> filenames of 
> > length > 7
> > 
> > I found an archived post which seems to be identical to my issue.
> > However, this is quite old and there never seemed to be any 
> > resolution.
> > 
> > http://www.infradead.org/pipermail/linux-mtd/2006-September/01
> > 6491.html
> > 
> > If I mount a filesystem that has filenames greater than 7 
> characters 
> > in length, the files are corrupted when I mount.
> > In my case, I am making a
> > JFFS2 image with mkfs.jffs2 and flashing it in with u-boot.  
> > However, I have attached a workflow where I erase the Flash 
> and create 
> > a new filesystem completely within Linux and it gives the same 
> > behavior.  I can list the files with the 'ls'
> > command from within u-boot.  If I mount from within Linux, and then 
> > reboot into u-boot, it will not display any files that had 
> a filename 
> > greater than 7 characters.
> > 
> > I enabled the MTD debug verbosity at level 2 for the 
> attached example 
> > session.
> > 
> > I am running on a custom board with a MPC5121 and Linux 2.6.33.4.
> > 
> > Thanks in advance for any help.
> 
> 
> Sorry for the jumbled mess.  Looks like the line endings are 
> messed up.
> Trying again.  I also provided this as an attachment in case 
> it gets messed up again.

Once again sorry for the mess.

I tried this again with the DENX-v2.6.34 tag in the DENX git repository
(git://git.denx.de/linux-2.6-denx.git).  The only modification I made
was to add my dts file.  I still get the same issue I had before.

I've attached my kernel config if that gives any clues.

Are there any thoughts on what may be causing this?

Thanks.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kernel.config
Type: application/octet-stream
Size: 25320 bytes
Desc: kernel.config
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20100624/81c2e4a3/attachment-0001.obj>