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>,
	Btrfs ML <linux-btrfs@vger.kernel.org>
Subject: Re: SLES 11 SP4: can't mount btrfs
Date: Tue, 24 Oct 2017 10:05:07 -0400	[thread overview]
Message-ID: <a4c7ccd2-c9ab-8a20-4156-f0f756aced81@gmail.com> (raw)
In-Reply-To: <006b01d34ccb$ee56bbd0$cb043370$@helmholtz-muenchen.de>

On 2017-10-24 09:28, Lentes, Bernd wrote:
> 
>> -----Original Message-----
>> From: Austin S. Hemmelgarn [mailto:ahferroin7@gmail.com]
>> Sent: Tuesday, October 24, 2017 1:53 PM
>> To: Adam Borowski <kilobyte@angband.pl>; Lentes, Bernd
>> <bernd.lentes@helmholtz-muenchen.de>
>> Cc: Btrfs ML <linux-btrfs@vger.kernel.org>
>> Subject: Re: SLES 11 SP4: can't mount btrfs
>>
>> I think partimage _might_ have BTRFS support by now, and if so, that's
>> likely to be the best you can get for quite some time.
> 
> Unfortunately not: http://www.partimage.org/Supported-Filesystems/
> 
>>> It depends on what you use subvolumes for.
>> And this is the important part.  If you're just using them to segregate
>> workloads (like I do), or exclude things from snapshots (like I used to do
>> when I was using snapshots for backups), then any old backup program is
>> fine as long as you know enough to replicate the subvolume layout when
>> extracting (if you need the same layout that is).  I'm actually working on
>> a
>> script to automate this for file-level backups (stuff like Amanda, Bareos,
>> and borgbackup), but I don't have anything ready to share yet.>
> 
> There seems to be no backup solution which supports BTRFS in a way that I
> can just restore the complete partition with all subvolumes, snapshots ?
> That's bad. A fs can also get corrupt in certain circumstances.
> I'd like to have a solution which offers me the possibility to restore a
> root partition in a reasonable time (some hours maximum), completely. Not
> doing many stuff before/afterwards. It seems that's not possible withBTRFS.
A short-term alternative, if you've got a full backup of what SLES 
mounts as /, is to run a regular install, boot the system, and then 
extract the backup on top of /.  It's not perfect, but it should work 
well enough.

As mentioned, I'm working on a script to handle this for tools like 
Amanda and Bareos.  I plan to send a message out on the list when that's 
sufficiently working that I think it's safely usable, I can make sure 
you're on CC for that message as well if you like.  I hoped to have 
something later this week, but things are busier than expected at work 
this week, so it might be a while.
> 
> And Btrfs check is still limited in what it can do.

  reply	other threads:[~2017-10-24 14:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 17:43 SLES 11 SP4: can't mount btrfs Lentes, Bernd
2017-10-19 18:57 ` Lentes, Bernd
2017-10-19 20:04 ` Chris Murphy
2017-10-20  4:09   ` Andrei Borzenkov
2017-10-20 17:26     ` Lentes, Bernd
2017-10-20 18:40       ` Lentes, Bernd
2017-10-21  2:31         ` Duncan
2017-10-21 11:46           ` Lentes, Bernd
2017-10-21 18:07             ` Adam Borowski
2017-10-22 10:36               ` Lentes, Bernd
2017-10-24 11:53               ` Austin S. Hemmelgarn
2017-10-24 13:28                 ` Lentes, Bernd
2017-10-24 14:05                   ` Austin S. Hemmelgarn [this message]
2017-10-24 16:43                     ` Lentes, Bernd
2017-10-26 12:18                       ` Lentes, Bernd
2017-10-26 12:55                         ` Peter Grandi
2017-10-26 16:37                           ` Lentes, Bernd
2017-10-26 20:48                             ` Peter Grandi
2017-10-26 16:51                         ` Andrei Borzenkov
2017-10-26 18:01                           ` Lentes, Bernd
2017-10-24 14:12                 ` Andrei Borzenkov
2017-10-24 14:20                   ` Austin S. Hemmelgarn
2017-10-20  6:32   ` Duncan

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=a4c7ccd2-c9ab-8a20-4156-f0f756aced81@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).