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: Fri, 20 Oct 2017 19:26:20 +0200 (CEST) [thread overview]
Message-ID: <00a601d349c8$8bde60d0$a39b2270$@helmholtz-muenchen.de> (raw)
In-Reply-To: <77b2d2c6-730e-62a5-93d1-4e40b51bc131@gmail.com>
> -----Original Message-----
> From: Andrei Borzenkov [mailto:arvidjaar@gmail.com]
> Sent: Friday, October 20, 2017 6:09 AM
> To: Chris Murphy <lists@colorremedies.com>; Lentes, Bernd
> <bernd.lentes@helmholtz-muenchen.de>
> Cc: Btrfs ML <linux-btrfs@vger.kernel.org>
> Subject: Re: SLES 11 SP4: can't mount btrfs
>
> 19.10.2017 23:04, Chris Murphy пишет:
> > Btrfs
> > is not just supported by SUSE, it's the default file system.
> >
>
> It is default choice for root starting with SLES12, not in SLES11. But
> yes, it
> should still be supported.
>
> I do not hold my breath though. For all I can tell transid errors are
> usually
> fatal and if this is root, it may be easier and faster to just reinstall.
Hi Andrei,
thanks for that info. So I will not waste my time and restore from a backup.
Or fresh installation with SLES 12 SP3 on my two cluster nodes, because SLES
11 SP4 is pretty old and support ends in beginning of 2019.
I also found the culprit for the disaster: the battery from the write-cache
of the RAID-Controller was empty, I ordered a new one.
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-20 17:26 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 [this message]
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
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='00a601d349c8$8bde60d0$a39b2270$@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).