linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 0/2] btrfs-progs: fi: enable fi usage for filesystem top of seed device
@ 2017-10-23  4:43 Misono, Tomohiro
  2017-10-23  4:44 ` [PATCH 1/2] btrfs-progs: fi: move dev_to_fsid() to cmds-fi-usage for later use Misono, Tomohiro
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Misono, Tomohiro @ 2017-10-23  4:43 UTC (permalink / raw)
  To: linux-btrfs

Currently "fi usage" (and "dev usage") cannot run for the filesystem using
seed device.

This is because FS_INFO ioctl returns the number of devices excluding
seeds, but load_device_info() tries to access valid device from devid 0
to max_id, and results in accessing seeds too (thus causing mismatching
of number of devices).

Since only the size of non-seed devices is matter, fix this by just
skipping seed device by checking device's fsid and comparing it to the fsid
obtained by FS_INFO ioctl.

Tomohiro Misono (2):
 btrfs-progs: fi: move dev_to_fsid() to cmds-fi-usage for later use
 btrfs-progs: fi: enable fi usage for filesystem top of seed device

 cmds-fi-usage.c   | 44 ++++++++++++++++++++++++++++++++++++++++++++
 cmds-fi-usage.h   |  1 +
 cmds-filesystem.c | 27 ---------------------------
 3 files changed, 45 insertions(+), 27 deletions(-)

-- 
2.9.5


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2017-10-26 18:38 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-23  4:43 [PATCH 0/2] btrfs-progs: fi: enable fi usage for filesystem top of seed device Misono, Tomohiro
2017-10-23  4:44 ` [PATCH 1/2] btrfs-progs: fi: move dev_to_fsid() to cmds-fi-usage for later use Misono, Tomohiro
2017-10-24  1:41   ` Anand Jain
2017-10-23  4:45 ` [PATCH 2/2] btrfs-progs: fi: enable fi usage for filesystem top of seed device Misono, Tomohiro
2017-10-24  1:48   ` Anand Jain
2017-10-26 18:36 ` [PATCH 0/2] " David Sterba

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).