From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: update qgroups in drop snapshot
Date: Thu, 24 Sep 2015 05:47:17 +0000 (UTC) [thread overview]
Message-ID: <pan$ee265$966e1174$56994f91$9fe0b788@cox.net> (raw)
In-Reply-To: 20150923214926.GD17854@wotan.suse.de
Mark Fasheh posted on Wed, 23 Sep 2015 14:49:26 -0700 as excerpted:
> On Wed, Sep 23, 2015 at 09:40:42AM +0800, Qu Wenruo wrote:
>>
>> I'd prefer a more accurate calculation based on nodesize.
>> That would allow using any possible nodesize.
>
> How do we query nodesize? 'btrfs fi show' doesn't seem to give it.
btrfs-show-super reports nodesize. Note, however, that unlike
btrfs fi show, show-super is used on a device, not a (mounted) filesystem.
(A not-too-technical question I can answer, so I am. =:^)
--
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:[~2015-09-24 5:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 20:15 [PATCH 0/4] btrfs: update qgroups in drop snapshot Mark Fasheh
2015-09-22 20:15 ` [PATCH 1/4] Btrfs: use btrfs_get_fs_root in resolve_indirect_ref Mark Fasheh
2015-09-22 20:15 ` [PATCH 2/4] Btrfs: keep dropped roots in cache until transaction commit, V2 Mark Fasheh
2015-09-22 20:15 ` [PATCH 3/4] btrfs: Add qgroup tracing Mark Fasheh
2015-09-22 20:15 ` [PATCH 4/4] btrfs: qgroup: account shared subtree during snapshot delete Mark Fasheh
2015-11-02 1:59 ` Qu Wenruo
2015-11-03 23:56 ` Mark Fasheh
2015-11-04 1:10 ` Qu Wenruo
2015-09-22 21:12 ` [PATCH 0/4] btrfs: update qgroups in drop snapshot Mark Fasheh
2015-09-23 1:40 ` Qu Wenruo
2015-09-23 21:49 ` Mark Fasheh
2015-09-24 5:47 ` Duncan [this message]
2015-09-24 6:29 ` Qu Wenruo
2015-09-23 3:58 ` Qu Wenruo
2015-09-23 8:50 ` Holger Hoffstätte
2015-09-23 22:08 ` Mark Fasheh
2015-09-25 3:17 ` Qu Wenruo
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$ee265$966e1174$56994f91$9fe0b788@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).