Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2024 06:24:06 +0100
From:      Jamie Landeg-Jones <jamie@catflap.org>
To:        stable@FreeBSD.org, kostikbel@gmail.com, jamie@catflap.org, bob@proulx.com
Subject:   Re: mount -u removes "noatime"
Message-ID:  <202409030524.4835O6YH038625@donotpassgo.dyslexicfish.net>
In-Reply-To: <202409030519.4835JmmY038549@donotpassgo.dyslexicfish.net>
References:  <202409020139.4821dOrY070960@donotpassgo.dyslexicfish.net> <ZtX18qSceQMgQu3o@kib.kiev.ua> <202409030005.48305xQw024483@donotpassgo.dyslexicfish.net> <20240902181513360947654@bob.proulx.com> <202409030519.4835JmmY038549@donotpassgo.dyslexicfish.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Jamie Landeg-Jones <jamie@catflap.org> wrote:
>
> Unfortunately, your pessimism is warranted:
>
>  | root@catflap# mount -u -ocurrent,snapshot /root/tw /
>  | mount: /root/tw: mount option <current> is unknown: Invalid argument
>  | /dev/da0p3 on / (ufs, local, noatime, writes: sync 3365270 async 2800944, reads: sync 205251 async 10254, fsid 1fa69665dd23d4e8, vnodes: count 3963 )

So, maybe mksnap_ffs(8) should be used to create snapshots instead of mount -u. Does anyone know if there is any other subtle difference betwwen the two?

Cheers.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202409030524.4835O6YH038625>