linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
Cc: Btrfs ML <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-subv-backup v0.1b
Date: Tue, 31 Oct 2017 16:00:03 -0400	[thread overview]
Message-ID: <b248c184-c7c9-f352-15d1-98b8830a347d@gmail.com> (raw)
In-Reply-To: <2032233997.441324.1509479675722.JavaMail.zimbra@helmholtz-muenchen.de>

On 2017-10-31 15:54, Lentes, Bernd wrote:
> ----- On Oct 31, 2017, at 6:00 PM, Austin S. Hemmelgarn ahferroin7@gmail.com wrote:
> 
>> Assuming you're careful about how you install it (that is, put it in a
>> custom prefix that isn't in $PATH), you could always build a local
>> version of Python.  Once you've got that, it's pretty trivial to change
>> the #! line at the beginning of the script to point to the appropriate
>> location.
>>
>> For what it's worth, it shouldn't be _too_ hard to get the script
>> working with Python 2.7.  The only big syntax difference that's liable
>> to be an issue is the except clauses.  I'll take a look at this and see
>> if I can't get it working for both 3.X and 2.7.
> 
> Austin,
> 
> do i understand correctly what i've read on github, that your script is worthless for SLES because they mount the subvolumes ?
> "this of course does not work if you explicitly mount subvolumes, but the only distro I know of that does that is SUSE, and they do their own thing anyway."
It's not quite worthless, it just needs a bit more effort, although 
that's not _just_ because of the subvolumes being explicitly mounted. 
There's also the fact that SUSE has an odd mix of subvolumes outside of 
the subvolume that gets mounted as root, and ones inside, which makes 
handling a SUSE root filesystem extremely complicated (though this is 
only the case if you installed with snapshot support enabled).

In short, to use this reliably for the root filesystem for OpenSUSE and 
SLES, you need to mount the top level of the root filesystem somewhere, 
and then run the script on that (and that tree is what you should be 
backing up in an ideal situation as well).

I'll look at getting the README updated to be more clear about that and 
give more specific directions tomorrow.

      reply	other threads:[~2017-10-31 20:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 13:32 btrfs-subv-backup v0.1b Austin S. Hemmelgarn
2017-10-26 15:25 ` Marat Khalili
2017-10-26 15:55   ` Austin S. Hemmelgarn
2017-10-31 12:40 ` Lentes, Bernd
2017-10-31 13:59   ` Austin S. Hemmelgarn
2017-10-31 16:54     ` Lentes, Bernd
2017-10-31 17:00       ` Austin S. Hemmelgarn
2017-10-31 19:54         ` Lentes, Bernd
2017-10-31 20:00           ` Austin S. Hemmelgarn [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=b248c184-c7c9-f352-15d1-98b8830a347d@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=bernd.lentes@helmholtz-muenchen.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 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).