linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 19 Oct 2017 20:57:56 +0200 (CEST)	[thread overview]
Message-ID: <000001d3490c$2cef1ea0$86cd5be0$@helmholtz-muenchen.de> (raw)
In-Reply-To: <1844960059.7648040.1508435017395.JavaMail.zimbra@helmholtz-muenchen.de>


> -----Original Message-----
> From: linux-btrfs-owner@vger.kernel.org [mailto:linux-btrfs-
> owner@vger.kernel.org] On Behalf Of Lentes, Bernd
> Sent: Thursday, October 19, 2017 7:44 PM
> To: Btrfs ML <linux-btrfs@vger.kernel.org>
> Subject: SLES 11 SP4: can't mount btrfs
>
> Hi,
>
> this is the continuation of a thread i started on a SLES forum
> (https://forums.suse.com/showthread.php?10109-lv-with-btrfs-corrupt-
> some-tips-please), but i think this is the more appropriate place.
> I have a SLES 11 SP4 with a btrfs on top of a logical volume i can't mount
> anymore. The host was fenced in a two-node cluster, and the boot
> procedure can't mount the lv, and i reside in simple shell (i assume the
> one from initrd).
>
> I have a second nearly identical node, so i can give you some information:
>
> ha-idg-2:/etc/corosync # uname -a
> Linux ha-idg-2 3.0.101-84-default #1 SMP Tue Oct 18 10:32:51 UTC 2016
> (15251d6) x86_64 x86_64 x86_64 GNU/Linux
>
> ha-idg-2:/etc/corosync # rpm -qa|grep -i btrfs
> libbtrfs0-3.18.2-0.40.48
> btrfsmaintenance-0.1-3.1
> btrfsprogs-3.18.2-0.40.48
>
> I try to follow the recommendations on
> https://btrfs.wiki.kernel.org/index.php/Problem_FAQ.
>
> I booted the system now with knoppix 8.1, which has kernel 4.12.7 and
> btrfs-progs 4.7.3-1. Is that ok ?
> I tried:
>
> mount /dev/vg1/lv_root /lv_root -o recovery,ro and got:
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/vg1-
> lv_root,
>        missing codepage or helper program, or other error
>
>        In some cases useful info is found in syslog - try
>        dmesg | tail or so.
>
>
> and got via dmesg:
> [92518.955408] BTRFS info (device dm-0): disk space caching is enabled
> [92518.990561] BTRFS error (device dm-0): parent transid verify failed on
> 196314759168 wanted 793932 found 793496 [92518.990911] BTRFS error
> (device dm-0): parent transid verify failed on 196314759168 wanted
> 793932 found 793496 [92518.990919] BTRFS error (device dm-0): failed to
> read block groups: -5 [92519.070084] BTRFS error (device dm-0):
> open_ctree failed
>
> next step:
>
> root@Microknoppix:~# btrfs device scan
> Scanning for Btrfs filesystems
> root@Microknoppix:~#
>
> no result !?!
>
> Now i changed to https://btrfs.wiki.kernel.org/index.php/Restore:
>
> btrfs restore -smSvi /dev/vg1/lv_root /mnt/idg-
> 2/SysAdmin_AG_Wurst/recover/ha-idg-1/ |tee /mnt/idg-
> 2/SysAdmin_AG_Wurst/recover/ha-idg-1/recover.log
>
> I just started it. I get lines like:
> offset is 61440
> offset is 98304
> offset is 4096
> offset is 143360
> offset is 8192
> offset is 184320
>
> or
>
> Error searching /mnt/idg-2/SysAdmin_AG_Wurst/recover/ha-idg-
> 1/@/tmp/localhpsum/assets/doc/help/en
> Error searching /mnt/idg-2/SysAdmin_AG_Wurst/recover/ha-idg-
> 1/@/tmp/localhpsum/assets/doc/help/ja/images/callouts
>
> What does that mean ?
>
>
> Bernd
>

The process does not continue, but it's still visible with ps. Also top does 
not show that this process is consuming resources. iotop does not show any 
activity on my lv.
My logfile is unchanged for two hours. Does that mean that btrfs gave up or 
is it still struggling ?

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


  reply	other threads:[~2017-10-19 18:58 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 [this message]
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
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='000001d3490c$2cef1ea0$86cd5be0$@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).