From: Johannes Thumshirn <jthumshirn@suse.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, David Sterba <dsterba@suse.com>
Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 2/2] btrfs: provide an estimated number of inodes for statfs
Date: Fri, 25 Oct 2019 10:55:32 +0200 [thread overview]
Message-ID: <782f4439-1c74-86d5-afc3-cdac906e01d2@suse.de> (raw)
In-Reply-To: <f1ecf175-9b4f-36bb-add7-b95bc26bc5e5@gmx.com>
On 25/10/2019 02:56, Qu Wenruo wrote:
[...]
> Personally speaking, reporting 0 used and 0 free should be the proper
> way. User of the fs should be aware of dynamical fs which doesn't go
> fixed inodes.
>
> I really think it's BeeFS' job to change their behavior.
>
> Since there are more thing to consider when faking the used/free inodes.
I'm with you on this. It is something BeeGFS has to fix, but judging
from what other file-systems do, some do have a real fixed number of
inodes, some assign 0 or -1, some do not touch the variable at all and
some (i.e. xfs) fake a number. My role model was xfs here.
--
Johannes Thumshirn SUSE Labs Filesystems
jthumshirn@suse.de +49 911 74053 689
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2019-10-25 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 15:44 [PATCH 0/2] Provide an estimation of (free/total) inodes in statfs Johannes Thumshirn
2019-10-24 15:44 ` [PATCH 1/2] btrfs: remove cached space_info in btrfs_statfs() Johannes Thumshirn
2019-10-25 16:41 ` David Sterba
2019-10-24 15:44 ` [PATCH 2/2] btrfs: provide an estimated number of inodes for statfs Johannes Thumshirn
2019-10-25 0:56 ` Qu Wenruo
2019-10-25 8:55 ` Johannes Thumshirn [this message]
2019-10-25 10:05 ` David Sterba
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=782f4439-1c74-86d5-afc3-cdac906e01d2@suse.de \
--to=jthumshirn@suse.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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