From: David Sterba <dsterba@suse.cz>
To: Chris Mason <chris.mason@fusionio.com>
Cc: linux-btrfs@vger.kernel.org,
Alex Lyakas <alex.btrfs@zadarastorage.com>,
Josef Bacik <jbacik@fusionio.com>
Subject: Re: [PATCH] btrfs: commit transaction after deleting a subvolume
Date: Sun, 20 Oct 2013 19:21:54 +0200 [thread overview]
Message-ID: <20131020172154.GH1032@suse.cz> (raw)
In-Reply-To: <20131020121959.4917.92120@localhost.localdomain>
On Sun, Oct 20, 2013 at 08:19:59AM -0400, Chris Mason wrote:
> My objections are pretty similar to Josef's. But, there's no reason we
> can't change the progs to optionally trigger a commit.
Works for me, though I'm not clear what should be the default.
> What I want to avoid is bulk snapshot deletion triggering a commit for
> each individual snapshot.
I agree and came to the same conclusion later on.
david
prev parent reply other threads:[~2013-10-20 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 22:25 [PATCH] btrfs: commit transaction after deleting a subvolume David Sterba
2013-10-20 10:46 ` Alex Lyakas
2013-10-20 12:19 ` Chris Mason
2013-10-20 17:21 ` David Sterba [this message]
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=20131020172154.GH1032@suse.cz \
--to=dsterba@suse.cz \
--cc=alex.btrfs@zadarastorage.com \
--cc=chris.mason@fusionio.com \
--cc=jbacik@fusionio.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 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).