Hi Guillermo, On Wednesday 07 May 2014 19:22:33 Guillermo Rodriguez Garcia wrote: > I wanted to use the noatime option for the jffs2 filesystem that is used in > the default ptxdist / mini2440 configuration, and found the following > problem: > > I first tried to modify /env/config in barebox to pass rootflags=noatime in > the kernel bootargs parameter. > > This results in a kernel panic: > > jffs2: Error: unrecognized mount option 'noatime' or missing value > [...] > No filesystem could mount root, tried: jffs2 > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(31,3) > > However, if I boot normally (with the default bootargs) and then remount > the jffs2 filesystem with noatime, it works fine: > > $ mount -o remount,noatime /
What 'mount' command implementation do you use? http://lists.infradead.org/pipermail/linux-mtd/2011-September/037975.html > I am puzzled by this as according to the documentation [1], the rootflags > argument "allows you to give options pertaining to the mounting of the > root filesystem just as you would to the mount program". > > Looks like a kernel bug to me, but on the other hand it seems so obvious > that perhaps I am overlooking something. Or simply a missunderstanding. JFFS2 seems not updating the access time itself. https://forum.openwrt.org/viewtopic.php?id=21051 So it seems, this option is not required to make JFFS2 what you want it to do. BTW: I did not found any hint in the source code. But JFFS2 at all supports only very few mount options. Refer fs/jffs2/super.c, line 172, table "tokens". But I'm not sure what other filesystem layers on top of JFFS2 do. Regards, Juergen -- Pengutronix e.K. | Juergen Borleis | Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
