From: Nikolay Borisov <nborisov@suse.com>
To: Qu WenRuo <wqu@suse.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH v6 0/4] Introduce per-profile available space array to avoid over-confident can_overcommit()
Date: Wed, 29 Jan 2020 11:23:59 +0200 [thread overview]
Message-ID: <52054f1b-bfed-d709-16c9-ce7007f6f3df@suse.com> (raw)
In-Reply-To: <55af2fa3-0762-3893-90b4-e0b90a225d27@suse.com>
On 29.01.20 г. 7:19 ч., Qu WenRuo wrote:
> Hi David,
>
> Mind to merge the patchset for misc-next?
>
> As patches 1~4 are reviewed, and the last patch is not that complex to
> grasp, I guess it's time to finish the long existing df 0 space bug,
> with better RAID5/6 estimation for df.
>
>
> For the long discussion about whether we should set available space back
> to 0 when metadata is exhausting, I still tend not to do so, since
> metadata and data are separate resources.
Be that as it may users shouldn't really care about the distinction
between metadata/data space. What they should care is whether they can
create any new files, if metadata is exhausted they can't.
>
> Thanks,
> Qu
>
next prev parent reply other threads:[~2020-01-29 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 6:03 [PATCH v6 0/4] Introduce per-profile available space array to avoid over-confident can_overcommit() Qu Wenruo
2020-01-16 6:04 ` [PATCH v6 1/5] btrfs: Introduce per-profile available space facility Qu Wenruo
2020-01-16 16:14 ` Josef Bacik
2020-01-17 0:55 ` Qu Wenruo
2020-01-17 1:50 ` Josef Bacik
2020-01-17 1:54 ` Qu Wenruo
2020-01-17 2:00 ` Josef Bacik
2020-01-16 6:04 ` [PATCH v6 2/5] btrfs: space-info: Use per-profile available space in can_overcommit() Qu Wenruo
2020-01-16 6:04 ` [PATCH v6 3/5] btrfs: statfs: Use pre-calculated per-profile available space Qu Wenruo
2020-01-16 16:21 ` Josef Bacik
2020-01-16 6:04 ` [PATCH v6 4/5] btrfs: Reset device size when btrfs_update_device() failed in btrfs_grow_device() Qu Wenruo
2020-01-16 6:04 ` [PATCH v6 5/5] btrfs: volumes: Revert device used bytes when calc_per_profile_avail() failed Qu Wenruo
2020-01-29 5:19 ` [PATCH v6 0/4] Introduce per-profile available space array to avoid over-confident can_overcommit() Qu WenRuo
2020-01-29 9:23 ` Nikolay Borisov [this message]
2020-01-29 10:51 ` 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=52054f1b-bfed-d709-16c9-ce7007f6f3df@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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).