From: Chris Mason <clm@fb.com>
To: David Sterba <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Cc: Jeff Mahoney <jeffm@suse.com>, Josef Bacik <jbacik@fb.com>
Subject: Re: [PATCH 3/4][RFC] btrfs: export global block reserve size as space_info
Date: Mon, 10 Feb 2014 12:03:51 -0500 [thread overview]
Message-ID: <52F90677.90107@fb.com> (raw)
In-Reply-To: <21dfbfe3b1361092ad1dc286f636c1fff4a2a4f6.1391779611.git.dsterba@suse.cz>
On 02/07/2014 08:34 AM, David Sterba wrote:
> Introduce a block group type bit for a global reserve and fill the space
> info for SPACE_INFO ioctl. This should replace the newly added ioctl
> (01e219e8069516cdb98594d417b8bb8d906ed30d) to get just the 'size' part
> of the global reserve, while the actual usage can be now visible in the
> 'btrfs fi df' output during ENOSPC stress.
>
> The unpatched userspace tools will show the blockgroup as 'unknown'.
>
This wasn't in my rc2 pull because I wanted to sync up with Jeff on it.
I like the idea of combining this into SPACE_INFO, any objections?
-chris
next prev parent reply other threads:[~2014-02-10 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 13:33 [PATCH 0/4] Btrfs updates for 3.14-rc - sysfs, ioctl David Sterba
2014-02-07 13:33 ` [PATCH 1/4] btrfs: commit transaction after setting label and features David Sterba
2014-02-07 13:34 ` [PATCH 2/4] btrfs: reserve no transaction units in btrfs_ioctl_set_features David Sterba
2014-02-07 13:34 ` [PATCH 3/4][RFC] btrfs: export global block reserve size as space_info David Sterba
2014-02-10 17:03 ` Chris Mason [this message]
2014-04-04 14:56 ` Jeff Mahoney
2014-02-07 13:34 ` [PATCH 4/4] Revert "btrfs: add ioctl to export size of global metadata reservation" 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=52F90677.90107@fb.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.com \
--cc=jeffm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.