From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: delete recursivly subvolumes?
Date: Fri, 5 Jul 2019 21:56:39 +0200 [thread overview]
Message-ID: <20190705195639.GD23600@tik.uni-stuttgart.de> (raw)
In-Reply-To: <20190705195142.GQ32479@carfax.org.uk>
On Fri 2019-07-05 (19:51), Hugo Mills wrote:
> > Is there a command/script/whatever to snapshot (copy) a subvolume which
> > contains (somewhere) other subvolumes?
> >
> > Example:
> >
> > root@xerus:/test# btrfs_subvolume_list /test/ | grep /tmp
> > /test/tmp
> > /test/tmp/xx/ss1
> > /test/tmp/xx/ss2
> > /test/tmp/xx/ss3
> >
> > I want to have (with one command):
> >
> > /test/tmp --> /test/tmp2
> > /test/tmp/xx/ss1 --> /test/tmp2/xx/ss1
> > /test/tmp/xx/ss2 --> /test/tmp2/xx/ss2
> > /test/tmp/xx/ss3 --> /test/tmp2/xx/ss3
>
> Remember that this isn't quite so useful, because you can't make
> read-only snapshots in that structure.
ss1 ss2 and ss3 are indeed read-only snapshots!
Of course they do not contain other subvolumes.
> Generally, I'd recommend not having nested subvols at all, but to
> put every subvol independently, and mount them into the places you
> want them to be. That avoids a lot of the issues of nested subvols,
> such as the ones you're trying to deal with here.
*I* do it this way from the very beginning :-)
But I have *users* with *strange* ideas :-}
I need to handle their data.
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<20190705195142.GQ32479@carfax.org.uk>
next prev parent reply other threads:[~2019-07-05 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 19:39 delete recursivly subvolumes? Ulli Horlacher
2019-07-05 19:47 ` Ulli Horlacher
2019-07-05 19:51 ` Hugo Mills
2019-07-05 19:56 ` Ulli Horlacher [this message]
2019-07-05 20:02 ` Hugo Mills
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=20190705195639.GD23600@tik.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.de \
--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.