From: David Sterba <dsterba@suse.cz>
To: kreijack@inwind.it
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] BTRFS-PROG: recursively subvolume snapshot and delete
Date: Fri, 29 Nov 2013 19:07:45 +0100 [thread overview]
Message-ID: <20131129180745.GQ25312@suse.cz> (raw)
In-Reply-To: <52979821.60401@gmail.com>
On Thu, Nov 28, 2013 at 08:23:13PM +0100, Goffredo Baroncelli wrote:
> Definetely you are right. In fact this is true also for other tools like
> tar: they complaint if you remove/move/rename a file during the copy. We
> can work to increase the robustness of the process, to avoid strange
> behaviour when a subvolume is removed/moved/renamed.
>
> Anyway I am more afraid that we can't mix recursive and readonly snapshot.
Agreed, this would eg. need to toggle RO/RW status when needed, but this
does not sound very clean.
> Implementing the atomic recursive snapshot in the kernel, is out of my
> possibility; anyway basically this means that the filesystem is frozen
> until all the snapshot are done, which requires a finite time. In case
> of a high number of subvolumes this could be a problem.
High number of subvolumes to snapshot atomically will always be
problematic and a lazy userspace-based recursive snapshot might be
actually better regarding the impact on the rest of the system, but
without guaranteed atomicity.
But, I don't want to kill the whole idea just because there's some
scenario that's possible but hard to handle.
david
next prev parent reply other threads:[~2013-11-29 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 17:09 [PATCH] BTRFS-PROG: recursively subvolume snapshot and delete Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 1/7] Recursive btrfs sub snapshot/delete: create get_root_info() function Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 2/7] recursive btrfs sub snapshot/delete: create pathjoin() function Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 3/7] recursive btrfs snapshot/delete: create traverse_list_subvol_rec() Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 4/7] recursive btrfs subvol delete Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 5/7] recursively btrfs subvolume snapshot Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 6/7] btrfs subvolume snapshot -R: update man page Goffredo Baroncelli
2013-11-16 17:09 ` [PATCH 7/7] Document the -R switch for the "btrfs subvolume delete" command Goffredo Baroncelli
2013-11-25 21:23 ` [PATCH] BTRFS-PROG: recursively subvolume snapshot and delete Goffredo Baroncelli
2013-11-26 15:12 ` Konstantinos Skarlatos
2013-11-26 17:44 ` Goffredo Baroncelli
2013-11-27 9:15 ` Konstantinos Skarlatos
2013-11-27 17:04 ` Goffredo Baroncelli
2013-11-28 18:31 ` David Sterba
2013-11-28 19:23 ` Goffredo Baroncelli
2013-11-29 18:07 ` David Sterba [this message]
2013-11-29 19:09 ` Goffredo Baroncelli
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=20131129180745.GQ25312@suse.cz \
--to=dsterba@suse.cz \
--cc=kreijack@inwind.it \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.