From nobody Thu Mar 07 14:09:19 2024 X-Original-To: current@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 4TrB530nYzz5D53c for ; Thu, 7 Mar 2024 14:09:43 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:313::1:5]) (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-signature ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TrB524bzCz3x0y for ; Thu, 7 Mar 2024 14:09:42 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1709820577; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=pIczKGM0K3VexoXH1z4LhOyd5J6DbXAa8hTE+k+w6FQ=; b=UovWRMpkPzSpR1hCSvfMCkFEdKwnZpdbhEItBmPXfsq5Q4T3aPCpIhMMOI3bAmvmdyT0Se m0IluDnNP6rTRptUlgorwUy58K4eM2ZdI3aJxRhIYcpyOsWzvV0UW2Jr8bCaUwpOSbKcqK aMLK2ytyWfboA1WQtReldm946WbR3MtiuwMimsbtWKLLM4kHv3Hfx7oZ3F1xM7kTuGDj7z cEKeCr9z2UEJHhZLYo+tRkckOe9nMMTRjdmChfMZSw1qBeU8UR/ww2u93GwzyTtK0l+7Ag JexSqkJ2bpMJ56SKjO0vOctMQ0PPJm1dJu5BEb4wnFF4mRxEJrUsiZZCkoD9bg== Date: Thu, 07 Mar 2024 15:09:19 +0100 From: Alexander Leidinger To: Christos Chatzaras Cc: Current Subject: Re: Reason why "nocache" option is not displayed in "mount"? In-Reply-To: <22017329-8EA9-4477-B5DB-412ABA34788D@cretaforce.gr> References: <09bb45dea82d96c11f34cc48dda540dc@Leidinger.net> <22017329-8EA9-4477-B5DB-412ABA34788D@cretaforce.gr> Message-ID: <0fc7f06e0d58f95c43198630e0895232@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_8b8d1a49efb7536f4fe6706c064f4810"; micalg=pgp-sha256 X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:34240, ipnet:2a00:1828::/32, country:DE] X-Rspamd-Queue-Id: 4TrB524bzCz3x0y This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_8b8d1a49efb7536f4fe6706c064f4810 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-03-07 14:59, schrieb Christos Chatzaras: >> what is the reason why "nocache" is not displayed in the output of >> "mount" for nullfs options? >> >> # grep packages /etc/fstab.commit_leidinger_net >> /shared/ports/packages >> /space/jails/commit.leidinger.net/shared/ports/packages nullfs >> rw,noatime,nocache 0 0 >> >> # mount | grep commit | grep packages >> /shared/ports/packages on >> /space/jails/commit.leidinger.net/shared/ports/packages (nullfs, >> local, noatime, noexec, nosuid, nfsv4acls) >> >> Context: I wanted to check if poudriere is mounting with or without >> "nocache", and instead of reading the source I wanted to do it more >> quickly by looking at the mount options. > > In my setup, I mount the /home directory using nullfs with the nocache > option to facilitate access for certain jails. The primary reason for > employing nocache is due to the implementation of ZFS quotas on the > main system, which do not accurately reflect changes in file usage by > users within the jail unless nocache is used. When files are added or > removed by a user within jail, their disk usage wasn't properly updated > on the main system until I started using nocache. Based on this > experience, I'm confident that applying nocache works as expected in > your scenario as well. It does. The question is how to I _see_ that a mount point is _setup_ with nocache? In the above example the FS _is_ mounted with nocache, but it is _not displayed_ in the output. Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_8b8d1a49efb7536f4fe6706c064f4810 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmXpyp4ACgkQEg2wmwP4 2IYz4A//Ub8GLbwayEJ0E1G928O3DVv0oGso7Y9mtbMOW59LD/6bCCWg4+GrrfUg QcAPP/W46Nf7hVgBgDCxm7HdjWyHp5ZiOEFW0CjqyXgBKBEokfbkZE/2SATDBaZI zffn7O5fDAaLqrRkDdPRpzQZQ6t0ks5lHIuatUA+oVXmWxYx4Sp72EAgzTwdGAFq XAywc2IGK9TnvBqOKkSvI2IoOhiFdl/WBiiIfQtP/TfVjazRJQme3TFBC/JnODus AuIItjz8h+oVvXdqG0JcgQOPatAhYBW8j7cw1V41kjr2sNfEBZc7ZVIFGsGxt6Ct 3WFvvwQ/OH3OD6vo9GghRUnkDZG46Tf7lHaZ4msqDK7StGxAY8igOwBv2A0BaGE2 GZBjNayxk9dHjSnHQ/4BLMkyqmOGeEn0Vqd8PGR+zGSYGv9tkFQGX7aL99DqtCMi 1qt9rOpfMJhjUJYglCpth267wpTL5GlU+KplkqEGZAO02lSHVXcOTjz6o4Uu9ZLd nyQi/dwsOxJ+jYeMHycjY13uVtJrMstxzg+3uVZDXIIogLLkCOmLBaRZzbOxETgb Sfga23Eoi/6cYQuGHHSGWPuoxAL2htWYy/4pezDOieNmvZYjxxGIPAh44j8iyqzq NNew5pBxqhH2s+RAFK4j1+u0dJ/U2sz/tmsgHNJZKg4UFwSs4lI= =Hqe9 -----END PGP SIGNATURE----- --=_8b8d1a49efb7536f4fe6706c064f4810--