Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Felix Koop <fdp@fkoop.de>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Help needed to recover a RAID5 btrfs
Date: Tue, 26 May 2015 13:56:03 +0800	[thread overview]
Message-ID: <55640AF3.2090502@cn.fujitsu.com> (raw)
In-Reply-To: <508094243.133459.1432569980190.JavaMail.open-xchange@oxbsltgw09.schlund.de>

> Hello,
>
> I have a RAID5 filesystem where one disk has crashed. Now the filesystem is not
> recognized any more. Any help available?
>
> Here is some info:
>
> root@server:~# uname -a
> Linux server 4.0.0-1-amd64 #1 SMP Debian 4.0.2-1 (2015-05-11) x86_64 GNU/Linux
>
> root@server:~# btrfs --version
> btrfs-progs v4.0
>
> root@server:~# btrfs f sh /dev/Data1vg/afs0
> warning, device 3 is missing
> warning devid 3 not found already
> checksum verify failed on 1111813750784 found 18019A1D wanted FCE227AB
> checksum verify failed on 1111813750784 found 18019A1D wanted FCE227AB
> bytenr mismatch, want=1111813750784, have=65536
> Couldn't read tree root
Tree root is corrupted, which is not a good news.

> Label: none uuid: 7d4b023a-a1ef-4991-b01d-31e7c4fdfbcf
>   Total devices 3 FS bytes used 213.96GiB
>   devid 2 size 150.00GiB used 108.53GiB path /dev/mapper/Data1vg-afs0
>   devid 4 size 150.00GiB used 108.53GiB path /dev/mapper/Data3vg-afs0
>   *** Some devices missing
The device 3, I guest it's /dev/mapper/data2vg-afs0, does it still 
exists in /dev/mapper?
>
> btrfs-progs v4.0
>
> root@server:~# mount -o degraded -r /dev/Data1vg/afs0 /mnt
> mount: wrong fs type, bad option, bad superblock on /dev/mapper/Data1vg-afs0,
>   missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog – try
>   dmesg | tail or so.
>
> root@server:~# dmesg | tail
> [104991.996065] BTRFS: open_ctree failed
> [105527.836798] blk_update_request: I/O error, dev fd0, sector 0
> [105527.839477] floppy: error -5 while reading block 0
> [105555.615991] BTRFS info (device dm-52): allowing degraded mounts
> [105555.616000] BTRFS info (device dm-52): disk space caching is enabled
> [105555.665644] BTRFS: bdev (null) errs: wr 38, rd 0, flush 0, corrupt 0, gen 0
> [105556.213570] BTRFS (device dm-52): bad tree block start 14290338419558610620
> 1111828267008
> [105556.216649] BTRFS (device dm-52): bad tree block start 14290338419558610620
> 1111828267008
> [105556.219364] BTRFS: Failed to read block groups: -5
> [105556.236056] BTRFS: open_ctree failed
>
>
> If more info is needed, just tell me what I should do. Thanks.
Need some extra info:
  btrfs-show-super -a -f /dev/mapper/Data1vg-afs0
  btrfs-show-super -a -f /dev/mapper/Data2vg-afs0 (If that is device3 
and exists)
  btrfs-show-super -a -f /dev/mapper/Data3vg-afs0

Maybe we can use old super to restore it to a mountable status.

If you have spare space to backup all the 3 devices, it's recommended to 
do it, as some repair tips may cause some write into disk, and may even 
make things worse.

Thanks,
Qu

>
> ---
>
> Kind greetings
>
> Felix Koop
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  parent reply	other threads:[~2015-05-26  5:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 16:06 Help needed to recover a RAID5 btrfs Felix Koop
2015-05-26  5:38 ` Duncan
2015-05-26  5:56 ` Qu Wenruo [this message]
2015-05-26 20:15   ` Felix Koop
2015-05-30 12:03     ` Felix Koop
2015-05-26 22:44 ` Omar Sandoval

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=55640AF3.2090502@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=fdp@fkoop.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