From: Mark Fasheh <mfasheh@suse.de>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org, jbacik@fb.com,
clm@fb.com, david@fromorbit.com
Subject: Re: [RFC][PATCH] btrfs: add ioctl to monitor subvolume dropping
Date: Tue, 6 Oct 2015 10:09:26 -0700 [thread overview]
Message-ID: <20151006170926.GC1044@wotan.suse.de> (raw)
In-Reply-To: <20151006082552.GA7734@twin.jikos.cz>
On Tue, Oct 06, 2015 at 10:25:52AM +0200, David Sterba wrote:
> On Thu, Oct 01, 2015 at 02:30:47PM -0700, Mark Fasheh wrote:
> > At the moment, userspace has no way of knowing when a snapshot is finally
> > removed. This has become a problem when writing tests for btrfs,
> >
> > http://article.gmane.org/gmane.comp.file-systems.fstests/1239/
>
> In the meantime the command 'btrfs subvolume sync /path id' has been
> implemented which does what you need, without the new ioctl.
Ahh ok I didn't see that I'll take a look, thanks.
>
> Also, you can query root_item::drop_progress directly through the
> SEARCH_TREE ioctl as well.
Yeah I realized this after I sent the patch but it seems like we don't need
either approach now if I can just wait with 'subvolume sync'
--Mark
--
Mark Fasheh
next prev parent reply other threads:[~2015-10-06 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201510020624.ABe5GlB7%fengguang.wu@intel.com>
2015-10-01 21:30 ` [RFC][PATCH] btrfs: add ioctl to monitor subvolume dropping Mark Fasheh
2015-10-01 22:26 ` [RFC PATCH] btrfs: drop_status_lock can be static kbuild test robot
2015-10-06 8:25 ` [RFC][PATCH] btrfs: add ioctl to monitor subvolume dropping David Sterba
2015-10-06 17:09 ` Mark Fasheh [this message]
2015-10-06 19:42 ` Mark Fasheh
2015-10-07 9:46 ` 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=20151006170926.GC1044@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=clm@fb.com \
--cc=david@fromorbit.com \
--cc=dsterba@suse.cz \
--cc=jbacik@fb.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).