From: "Tom Schwindl" <schwindl@posteo.de>
To: наб <nabijaczleweli@nabijaczleweli.xyz>,
"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: <linux-man@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] statvfs.3: note f_favail = f_ffree on Linux
Date: Wed, 05 Jul 2023 13:57:53 +0000 [thread overview]
Message-ID: <CTUAI5KRV29O.19BHQPHOW5Y4@morphine> (raw)
In-Reply-To: <xve2ekfim2chw5s47wf76wtnan3khk5d4jdow4jkmlt7ifa2oy@uicda22mmppt>
On Sat Jun 24, 2023 at 2:39 AM CEST, наб wrote:
> Quoting myself from #musl:
> 01:59:40 hm, I think this was just invented for symmetry with bfree/bavail
> 02:00:46 FFS has minfree for space but nothing equivalent for inodes
> 02:32:31 (this is mirrored in ext4;
> a global grep over DragonFlyBSD and the illumos gate
> showed just NFSv3 forwarding from the server;
> OpenBSD always sets it to the same thing as f_ffree;
> oddly, NetBSD /does/ calculate it differently
> for LFS and FFS but due to queued writes or
> w/e not because of root reservation;
> and as expected a lot of "/* what to put in here? */"
> and "// XXX same??")
>
> Link: https://lore.kernel.org/linux-man/f54kudgblgk643u32tb6at4cd3kkzha6hslahv24szs4raroaz@ogivjbfdaqtb/t/#u
> Signed-off-by: Ahelenia Ziemiańska <nabijaczleweli@nabijaczleweli.xyz>
> ---
> man3/statvfs.3 | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/man3/statvfs.3 b/man3/statvfs.3
> index b1f0e7545..272ee5391 100644
> --- a/man3/statvfs.3
> +++ b/man3/statvfs.3
> @@ -227,6 +227,14 @@ .SH NOTES
> .BR statvfs ()
> with the argument
> .IR path .
> +.PP
> +Under Linux,
> +.I f_favail
> +is always the same as
> +.IR f_ffree ,
> +and there's no way for a file-system to report otherwise.
s/file-system/filesystem/ as that's what's used elsewhere.
> +This is not an issue, since no filesystems with an i-node
> +root reservation exist.
s/i-node/inode/ for the same reason.
> .SH STANDARDS
> POSIX.1-2008.
> .SH HISTORY
--
Best Regards,
Tom Schwindl
next prev parent reply other threads:[~2023-07-05 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 19:58 [f]statfs(2) shaded as deprecated? наб
2023-06-23 20:08 ` Alejandro Colomar
2023-06-23 21:00 ` [PATCH 1/2] statfs.2: unshade as deprecated, but direct to statvfs(3) наб
2023-06-23 21:00 ` [PATCH 2/2] statvfs.3: note f_favail = f_ffree on Linux наб
2023-06-24 0:39 ` [PATCH v2 " наб
2023-07-05 13:57 ` Tom Schwindl [this message]
2023-07-08 17:11 ` Alejandro Colomar
2023-07-08 20:01 ` [PATCH v3 " наб
2023-07-15 13:41 ` Alejandro Colomar
2023-07-18 11:43 ` [PATCH v2 " Alejandro Colomar
2023-07-18 11:48 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CTUAI5KRV29O.19BHQPHOW5Y4@morphine \
--to=schwindl@posteo.de \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox