All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glenn Trigg <ggtrigg@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: help request for an unmountable raid1 filesystem
Date: Sun, 10 Mar 2019 08:35:48 +1100	[thread overview]
Message-ID: <CAG3pWAmvekNpnBsQTaMrefKe6pvMSZjPm+SOxnKkMkpGO_1msQ@mail.gmail.com> (raw)

Hello,

I had some random machine freezing events which I suspected was due to
issues with a raid1 filesystem and kernel module crashes. I attempted
to use the information available to get the filesystem into a good
state where "btrfs check" and "btrfs scrub" would not have any errors,
however I fear things have become worse.

The current state of things is that the filesystem won't mount at all now.

% mount -r /dev/sda1 /data
mount: /data: can't read superblock on /dev/sda1.

and dmesg says:

[15944.017629] BTRFS info (device sda1): disk space caching is enabled
[15944.017632] BTRFS info (device sda1): has skinny extents
[15944.024480] BTRFS info (device sda1): bdev /dev/sda1 errs: wr 0, rd
0, flush 0, corrupt 1, gen 0
[15944.024487] BTRFS info (device sda1): bdev /dev/sdb1 errs: wr 0, rd
0, flush 0, corrupt 4, gen 0
[15944.029292] BTRFS error (device sda1): parent transid verify failed
on 628168376320 wanted 37601 found 37700
[15944.029466] BTRFS error (device sda1): parent transid verify failed
on 628168376320 wanted 37601 found 37700

Other system information is:
% uname -a
Linux izen 4.18.0-16-generic #17-Ubuntu SMP Fri Feb 8 00:06:57 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

% btrfs --version
btrfs-progs v4.16.1

% btrfs fi show
Label: 'root'  uuid: 65fd7f11-4f60-435f-928b-6d15f12bc417
Total devices 1 FS bytes used 101.75GiB
devid    1 size 232.88GiB used 232.85GiB path /dev/nvme0n1p1

Label: 'data'  uuid: d5e50511-3e31-4de6-ba37-c5841895be9f
Total devices 2 FS bytes used 830.44GiB
devid    1 size 1.82TiB used 669.03GiB path /dev/sda1
devid    2 size 1.82TiB used 817.06GiB path /dev/sdb1

% btrfs check /dev/sda1
Checking filesystem on /dev/sda1
UUID: d5e50511-3e31-4de6-ba37-c5841895be9f
checking extents
parent transid verify failed on 628168343552 wanted 28163 found 37700
parent transid verify failed on 628168343552 wanted 28163 found 37700
parent transid verify failed on 628168343552 wanted 28163 found 37700
parent transid verify failed on 628168343552 wanted 28163 found 37700
Ignoring transid failure
bad block 628168343552
ERROR: errors found in extent allocation tree or chunk allocation
checking free space cache
cache and super generation don't match, space cache will be invalidated
checking fs roots
root 5 root dir 256 not found
ERROR: errors found in fs roots
found 528138240 bytes used, error(s) found
total csum bytes: 0
total tree bytes: 1785856
total fs tree bytes: 1064960
total extent tree bytes: 81920
btree space waste bytes: 606983
file data blocks allocated: 215220224
 referenced 215220224

% btrfs rescue super-recover /dev/sda1
All supers are valid, no need to recover

Where do I go from here?

Regards,
Glenn

             reply	other threads:[~2019-03-09 21:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-09 21:35 Glenn Trigg [this message]
2019-03-23  0:45 ` help request for an unmountable raid1 filesystem Glenn Trigg
2019-03-29  0:53   ` Glenn Trigg
2019-03-29  2:27 ` Chris Murphy
2019-03-29  3:21   ` Chris Murphy
2019-03-30 23:43   ` Glenn Trigg
2019-03-31 21:34     ` Chris Murphy
2019-04-01  5:48       ` Glenn Trigg
2019-04-01 17:14         ` Chris Murphy
2019-04-05  5:51           ` Glenn Trigg
2019-04-05  6:44             ` Chris Murphy
2019-04-06  0:37               ` Glenn Trigg

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=CAG3pWAmvekNpnBsQTaMrefKe6pvMSZjPm+SOxnKkMkpGO_1msQ@mail.gmail.com \
    --to=ggtrigg@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.