From: Jens Rosenboom <j.rosenboom@syseleven.de>
To: linux-btrfs@vger.kernel.org
Subject: btrfs lacking inode or file count?
Date: Mon, 07 Mar 2011 17:17:49 +0100 [thread overview]
Message-ID: <4D75052D.7050704@syseleven.de> (raw)
I'm just starting to do some testing with btrfs and I noticed that "df
-i" doesn't give any sensible output:
backup01 ~ # df -i /mnt/backup01-p1/
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/mapper/backup01p1
0 0 0 - /mnt/backup01-p1
backup01 ~ # df -h /mnt/backup01-p1/
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/backup01p1
20T 444G 20T 3% /mnt/backup01-p1
backup01 ~ # btrfs file show
Label: 'backup01-p1' uuid: d6a87326-b28b-425a-9c80-0e4b31dfe951
Total devices 1 FS bytes used 431.13GB
devid 1 size 20.00TB used 454.29GB path /dev/dm-3
Is it too difficult to provide the number of inodes in use or is this
just not yet implemented?
If inodes are difficult, would the number of files (ideally per
subvolume) be easier to obtain?
next reply other threads:[~2011-03-07 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 16:17 Jens Rosenboom [this message]
2011-03-07 17:38 ` btrfs lacking inode or file count? Christian Kujau
2011-03-08 9:45 ` Jens Rosenboom
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=4D75052D.7050704@syseleven.de \
--to=j.rosenboom@syseleven.de \
--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;
as well as URLs for NNTP newsgroup(s).