From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: device delete progress
Date: Sun, 21 Sep 2014 08:34:33 +0000 (UTC) [thread overview]
Message-ID: <pan$1d8a8$448bb26c$d55fc521$929be7e0@cox.net> (raw)
In-Reply-To: 201409211209.11875.russell@coker.com.au
Russell Coker posted on Sun, 21 Sep 2014 12:09:11 +1000 as excerpted:
> We need to have a way to determine the progress of a device delete
> operation.
> Also for a balance of a RAID-1 that has more than 2 devices it would be
> good to know how much space is used on each device.
>
> Could btrfs fi df be extended to show information separately for each
> device?
btrfs fi show should give you at least some minimal per-device stats,
today. Enough to at least have some idea of the progress of a balance
when adding/removing devices.
Longer term, there has been discussion of extending/changing the fi df
format and making it far more verbose, including the information found in
btrfs fi show as well, and making everything potentially per-device. I
hadn't paid a whole lot of attention to the details, however.
Alternatively, leave df more or less as it is (perhaps extending it a bit
but attempting not to kill existing scripts using it) and put the detail
in a new btrfs filesystem usage. This sounds rather more reasonable to
me.
Either way the idea is to give people a single command that combines the
current output of fi show and fi df, ideally displaying per-device and
filesystem totals both, in enough verbosity to avoid the unintuitive and
arcane btrfs specific knowledge required today to interpret it.
I had originally presumed that such a change would happen before the
experimental labels came off, but it didn't. I don't know the timetable
for it now, or even if it's still planned, as IIRC the discussion died
away back in the btrfs-progs 3.12 era and I expected to see it in 3.14
and it wasn't there, so I don't know...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-09-21 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 2:09 device delete progress Russell Coker
2014-09-21 8:34 ` Duncan [this message]
2014-09-22 9:49 ` David Sterba
2014-09-22 16:29 ` Duncan
2014-09-22 19:23 ` Duncan
2014-09-21 17:12 ` Chris Murphy
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='pan$1d8a8$448bb26c$d55fc521$929be7e0@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).