From nobody Tue Sep 03 00:27:36 2024 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4WyRKX4swMz5VJwD for ; Tue, 03 Sep 2024 00:27:44 +0000 (UTC) (envelope-from rwp@proulx.com) Received: from havoc.proulx.com (havoc.proulx.com [198.99.81.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4WyRKW32x2z4kdV for ; Tue, 3 Sep 2024 00:27:43 +0000 (UTC) (envelope-from rwp@proulx.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=proulx.com header.s=dkim2048 header.b=Z1d0xQbS; dmarc=pass (policy=none) header.from=proulx.com; spf=pass (mx1.freebsd.org: domain of rwp@proulx.com designates 198.99.81.74 as permitted sender) smtp.mailfrom=rwp@proulx.com Received: from joseki.proulx.com (localhost [127.0.0.1]) by havoc.proulx.com (Postfix) with ESMTPS id ABFF0236 for ; Mon, 2 Sep 2024 18:27:36 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proulx.com; s=dkim2048; t=1725323256; bh=U80HaUAfAnap7SypFe0Oy6MEXPYM4eHuBEH96VTSE88=; h=Date:From:To:Subject:References:In-Reply-To:From; b=Z1d0xQbSfJPgWJWfMx4Z6zgZk7PahPY6zoMCIPNiR7aZESVoo65ANTEQAfmlHI3bQ V6KbozwFOV7jk6qRF1wo4ujI9b4X/VS/7jNxWBy5eIPxVvBvog0/KI0kXmdYlcXCxZ D3O+Le0pZa0Byca8FdxMMRgSQu9ssYwVTayOrbTk+88Rj7yGCsTpkMslPZFg+ee3qF RZW1FOuC7rG/3LstcB5jGXpjtttm4zo2HtlO1cCk3drewbhd5vjTUH92a2r0GMfiRL /eLBOXqfcGPjIWNSKx5cAzRlDsJlTxP2QPlLcDTvNVTAWa2wEbWiCtfA2gW+h+ZCeV +scyHMXaPnKdA== Received: from madness.proulx.com (madness.proulx.com [192.168.230.122]) by joseki.proulx.com (Postfix) with ESMTP id 26F177A00E for ; Mon, 2 Sep 2024 18:27:36 -0600 (MDT) Received: by madness.proulx.com (Postfix, from userid 1000) id 1B2E4D04C6; Mon, 02 Sep 2024 18:27:36 -0600 (MDT) Date: Mon, 2 Sep 2024 18:27:36 -0600 From: Bob Proulx To: stable@freebsd.org Subject: Re: mount -u removes "noatime" Message-ID: <20240902181513360947654@bob.proulx.com> References: <202409020139.4821dOrY070960@donotpassgo.dyslexicfish.net> <202409030005.48305xQw024483@donotpassgo.dyslexicfish.net> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202409030005.48305xQw024483@donotpassgo.dyslexicfish.net> X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.70 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[proulx.com,none]; FORGED_SENDER(0.30)[bob@proulx.com,rwp@proulx.com]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[proulx.com:s=dkim2048]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; ASN(0.00)[asn:397142, ipnet:198.99.80.0/22, country:US]; MISSING_XM_UA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCVD_TLS_LAST(0.00)[]; FROM_NEQ_ENVFROM(0.00)[bob@proulx.com,rwp@proulx.com]; FROM_HAS_DN(0.00)[]; MLMMJ_DEST(0.00)[stable@freebsd.org]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[stable@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[proulx.com:+] X-Rspamd-Queue-Id: 4WyRKW32x2z4kdV 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 me though. TIL that I should always use either current or fstab. mount -u -o current / Or mount -u -o fstab / And then make modifications from those references. mount -u -o current,noatime / Or mount -u -o fstab,noatime / > As it stands, how do we preserve atime status without scripting > around it? Maybe at least the manual page should make this clearer? 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. mount -u -o current,snapshot ... I don't have a system to test this type of snapshot upon. Bob