From: "Lentes, Bernd" <bernd.lentes@helmholtz-muenchen.de>
To: "Btrfs ML" <linux-btrfs@vger.kernel.org>
Subject: RE: SLES 11 SP4: can't mount btrfs
Date: Tue, 24 Oct 2017 18:43:46 +0200 (CEST) [thread overview]
Message-ID: <001001d34ce7$42c576f0$c85064d0$@helmholtz-muenchen.de> (raw)
In-Reply-To: <a4c7ccd2-c9ab-8a20-4156-f0f756aced81@gmail.com>
> -----Original Message-----
> From: linux-btrfs-owner@vger.kernel.org
> [mailto:linux-btrfs-owner@vger.kernel.org] On Behalf Of Austin S.
> Hemmelgarn
> Sent: Tuesday, October 24, 2017 4:05 PM
> To: Lentes, Bernd <bernd.lentes@helmholtz-muenchen.de>; Btrfs ML
> <linux-btrfs@vger.kernel.org>
> Subject: Re: SLES 11 SP4: can't mount btrfs
>
> 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.
That's what I'm currently trying. I will keep you informed.
> 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.
Please put me on cc. That would be great. Thanks.
Bernd
Helmholtz Zentrum Muenchen
Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH)
Ingolstaedter Landstr. 1
85764 Neuherberg
www.helmholtz-muenchen.de
Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe
Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons Enhsen
Registergericht: Amtsgericht Muenchen HRB 6466
USt-IdNr: DE 129521671
next prev parent reply other threads:[~2017-10-24 16:43 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
2017-10-24 16:43 ` Lentes, Bernd [this message]
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='001001d34ce7$42c576f0$c85064d0$@helmholtz-muenchen.de' \
--to=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).