From: Johannes Thumshirn <jthumshirn@suse.de>
To: David Sterba <dsterba@suse.com>
Cc: Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>,
Johannes Thumshirn <jthumshirn@suse.de>
Subject: [PATCH 0/2] Provide an estimation of (free/total) inodes in statfs
Date: Thu, 24 Oct 2019 17:44:53 +0200 [thread overview]
Message-ID: <20191024154455.19370-1-jthumshirn@suse.de> (raw)
There is a user report on the BeeGFS mailing list, that it's impossible to run
BeeGFS on top of BTRFS.
This is because BeeGFS is storing it's meta-data either in the underlying
file-systems extended attributes or directly in an inode if it can make use of
inline inodes.
A more detailed description is in patch 2/2.
Without the patch applied:
rapido1:/# df -hTi /mnt/test
Filesystem Type Inodes IUsed IFree IUse% Mounted on
/mnt/test btrfs 0 0 0 - /mnt/test
With the patch applied on an empty fs:
rapido1:/# df -hTi /mnt/test
Filesystem Type Inodes IUsed IFree IUse% Mounted on
/dev/zram0 btrfs 1.6K 0 1.6K 0% /mnt/test
With the patch applied on a dirty fs:
rapido1:/# df -hTi /mnt/test
Filesystem Type Inodes IUsed IFree IUse% Mounted on
/dev/zram0 btrfs 1.6K 1.5K 197 88% /mnt/test
Johannes Thumshirn (2):
btrfs: remove cached space_info in btrfs_statfs()
btrfs: provide an estimated number of inodes for statfs
fs/btrfs/super.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.16.4
next reply other threads:[~2019-10-24 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 15:44 Johannes Thumshirn [this message]
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
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=20191024154455.19370-1-jthumshirn@suse.de \
--to=jthumshirn@suse.de \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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