From: Bruce Guenter <bruce@untroubled.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs subvolume delete --commit-after doesn't wait for deletions
Date: Fri, 6 Jan 2017 16:43:06 -0600 [thread overview]
Message-ID: <20170106224306.GA8756@untroubled.org> (raw)
In-Reply-To: <495af306-19bc-6af1-4411-e2eefe143891@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On Thu, Jan 05, 2017 at 10:03:17AM +0800, Qu Wenruo wrote:
> To wait the deletion finish, please use "btrfs filesystem sync".
That doesn't entirely work either. It does appear to wait for something,
but disk space available continues to increase after it exits.
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-01-06 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 1:46 btrfs subvolume delete --commit-after doesn't wait for deletions Bruce Guenter
2017-01-05 2:03 ` Qu Wenruo
2017-01-06 22:43 ` Bruce Guenter [this message]
2017-01-09 1:44 ` Qu Wenruo
2017-01-10 22:33 ` Bruce Guenter
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=20170106224306.GA8756@untroubled.org \
--to=bruce@untroubled.org \
--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).