From: Roman Mamedov <rm@romanrm.net>
To: "Piotr Pawłow" <pp@siedziba.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "Transaction commit" in btrfs sub del
Date: Thu, 23 Oct 2014 22:18:03 +0600 [thread overview]
Message-ID: <20141023221803.13832b4e@natsu> (raw)
In-Reply-To: <5449226E.606@siedziba.pl>
On Thu, 23 Oct 2014 17:44:46 +0200
Piotr Pawłow <pp@siedziba.pl> wrote:
> On 23.10.2014 16:24, Roman Mamedov wrote:
> > I was under impression that the "Transaction commit:" setting in 'btrfs sub
> > del' finally allows us to make it not return until all free space from the
> > snapshots that are being deleted, is completely freed up.
>
> This is not what "commit-each" or "commit-after" options do. These are
> only to make sure, that the deletion is commited and the subvolume
> doesn't reappear after a crash.
But is that not already ensured by a regular 'sync', or 'btrfs fi sync'?
> You probably want "subvolume sync" command, introduced in btrfs-progs 3.17:
>
> btrfs subvolume sync <path> [<subvol-id>...]
> Wait until given subvolume(s) are completely removed from the
> filesystem.
Oh right, *that*'s the one I was thinking of.
--
With respect,
Roman
next prev parent reply other threads:[~2014-10-23 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 14:24 "Transaction commit" in btrfs sub del Roman Mamedov
2014-10-23 15:44 ` Piotr Pawłow
2014-10-23 16:18 ` Roman Mamedov [this message]
2014-10-23 16:28 ` Wang Shilong
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=20141023221803.13832b4e@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=pp@siedziba.pl \
/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