Jamie Landeg-Jones wrote:
>
> Unfortunately, your pessimism is warranted:
>
> | root@catflap# mount -u -ocurrent,snapshot /root/tw /
> | mount: /root/tw: mount option is unknown: Invalid argument
> | /dev/da0p3 on / (ufs, local, noatime, writes: sync 3365270 async 2800944,
> reads: sync 20525
Bob Proulx wrote:
Hi Bob! Thanks for the info.
> I want to think that using -o current and then making modifications to
> current seems to be one possible way. But the man page also says,
> "When this option [snapshot] is used, all other options are ignored."
> So this shouldn't work.
>
> m
Jamie Landeg-Jones wrote:
> Konstantin Belousov wrote:
> > This is how mount update works. How otherwise would you remove noatime
> > from the options? It seems to be true for other 'flag' options as well.
>
> mount -u -o atime works.
>
> Thanks for the clarification. It seems counterintuitive to
Konstantin Belousov wrote:
> This is how mount update works. How otherwise would you remove noatime
> from the options? It seems to be true for other 'flag' options as well.
>
> Really nonoatime should work with nmount, but it probably does not.
mount -u -o atime works.
Thanks for the clarifi
On Mon, Sep 02, 2024 at 02:39:24AM +0100, Jamie Landeg-Jones wrote:
> I noticed some of my noatime mounts keep being reset to atime. Looking
> further, I found out the culprit was a snapshotting program running:
>
> mount -u -o snapshot
>
> It turns out, that just using -u causes noatime to be
