Setting noatime to mounted file systems

[Jeremy MJ]

How do I set a USB drive to use the mount flag noatime and have it
stick (without changing /etc/fstab and remounting every time I boot
up?). Also interested in making this persistent for the drives on
RAID1 since I don't need it there either. I know that relatime (the
default with alt-f) is more efficient than atime but, again, no need
for neither with what I'm running on my NAS, and I'll take any
performance I can get from this little box. And for the thumb drive,
any decrease in reads / writes = increase in life time.

I thought about putting a mount command to remount in the ffp script,
but is there a cleaner way than remounting after boot? If I add to the
ffp file, is it safe to remount the raid (probably a silly question,
but I worry about breaking stuff)?

Thanks for any help,

JM

[Joao Cardoso]

On Jan 21, 11:06 pm, Jeremy MJ <jeremy.mountainjohn...@gmail.com>
wrote:

> How do I set a USB drive to use the mount flag noatime and have it
> stick (without changing /etc/fstab and remounting every time I boot
> up?). Also interested in making this persistent for the drives on
> RAID1 since I don't need it there either. I know that relatime (the
> default with alt-f) is more efficient than atime but, again, no need
> for neither with what I'm running on my NAS, and I'll take any
> performance I can get from this little box. And for the thumb drive,
> any decrease in reads / writes = increase in life time.
>

There is currently no way of doing this through the web pages. fstab
is not saved in flash, only nfs and smb mounts are.

How about providing a mount options input field in the filesystem
maintenance web page? The mount options would be associated with the
fs throught its uuid and used at mount time. The options would be
saved in misc.conf, which is saved in flash.
The downside is that misc.conf might grow without bounds.

Any other ideas?

Every user will have its own special needs, but this seems reasonable.

[Jeremy MountainJohnson]

Glad you agree with the need. Based on the space concern, I almost think
that using drive space or a thumb drive and re-parsing fstab could also
be an decent option (albeit the redundancy). Otherwise is there a fail
safe way of using the flash space only if there is enough space? For
example, I can only save one settings file at any given time (it throws
an error if I try to save more than one file).

*Jeremy MountainJohnson*
jeremy.moun...@gmail.com <mailto:jeremy.moun...@gmail.com>

[Joao Cardoso]

> Otherwise is there a fail
> safe way of using the flash space only if there is enough space? For
> example, I can only save one settings file at any given time (it throws
> an error if I try to save more than one file).
>

There is a closed issue (in the code site) regarding this question,
please search and read it.

[Joao Cardoso]

On Jan 22, 5:37 pm, Joao Cardoso <whoami.jc...@gmail.com> wrote:
> On Jan 21, 11:06 pm, Jeremy MJ <jeremy.mountainjohn...@gmail.com>
> wrote:
>
> > How do I set a USB drive to use the mount flag noatime and have it
> > stick (without changing /etc/fstab and remounting every time I boot
> > up?). Also interested in making this persistent for the drives on
> > RAID1 since I don't need it there either. I know that relatime (the
> > default with alt-f) is more efficient than atime but, again, no need
> > for neither with what I'm running on my NAS, and I'll take any
> > performance I can get from this little box. And for the thumb drive,
> > any decrease in reads / writes = increase in life time.
>
> There is currently no way of doing this through the web pages. fstab
> is not saved in flash, only nfs and smb mounts are.
>
> How about providing a mount options input field in the filesystem
> maintenance web page? The mount options would be associated with the
> fs throught its uuid and used at mount time. The options would be
> saved in misc.conf, which is saved in flash.

The change is now svn commited. Not very throughly tested, though