Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Alexander Skwar <alexanders.mailinglists+nospam@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Creating recursive snapshots for all filesystems
Date: Fri, 3 May 2013 11:46:59 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130503T134340-902@post.gmane.org> (raw)
In-Reply-To: 20130503084822.GA22531@panda

Hi

Sander <sander <at> humilis.net> writes:

> 
> Alexander Skwar wrote (ao):
> > Where I'm hanging right now, is that I can't seem to figure out a
> > "bullet proof" way to find all the subvolumes of the filesystems I
> > might have.
> 
> > Is there an easier way to achieve what I want? I want to achieve:
> > 
> > Creating recursive snapshots for all filesystems
> 
> Not sure if this helps, but I have subvolid=0, which contains all my
> subvolumes, mounted under /.root/

Hm, not quite what I'm after and not nearly as easy as ZFS...

"Problem" with your approach: The admin has to maintain this. 
I was looking for something, which "maints itself", so to say.
And your approach also wouldn't scale if there are sub-subvolumes.

ZFS really is so much easier (at least regarding that).

Thanks a lot, though. It's a worthwhile idea.

Regards,
Alexander



  reply	other threads:[~2013-05-03 11:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 20:41 Creating recursive snapshots for all filesystems Alexander Skwar
2013-05-03  8:48 ` Sander
2013-05-03 11:46   ` Alexander Skwar [this message]
2013-05-05 11:05 ` Kai Krakow
2013-05-05 12:59   ` Alexander Skwar
2013-05-05 16:03     ` Kai Krakow
2013-05-05 16:19       ` Alexander Skwar
2013-05-09 20:41     ` nocow 'C' flag ignored after balance Kyle Gates
2013-05-10  5:15       ` Liu Bo
2013-05-10 13:58         ` Kyle Gates
2013-05-16 19:11           ` Kyle Gates
2013-05-17  7:04             ` Liu Bo
2013-05-17 14:38               ` Kyle Gates
2013-05-28 14:22               ` Kyle Gates
2013-05-29  1:55                 ` Liu Bo
2013-05-29  8:33                   ` Miao Xie
2013-05-30 16:40                     ` Kyle Gates
2013-05-30 16:40                   ` Kyle Gates

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=loom.20130503T134340-902@post.gmane.org \
    --to=alexanders.mailinglists+nospam@gmail.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