linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@inwind.it>
To: TheJay <obiwantje@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [REQ] Help to gain access to btrfsraid6 pool that won't mount
Date: Mon, 04 May 2015 23:25:19 +0200	[thread overview]
Message-ID: <5547E3BF.4090901@inwind.it> (raw)
In-Reply-To: <mi8452$i00$1@ger.gmane.org>

On 2015-05-04 17:44, TheJay wrote:
> $ uname -a
> Linux thejay-srv03 4.0.0-040000-generic #201504121935 SMP Sun Apr 12 
> 23:36:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
> 
> $ btrfs --version
> btrfs-progs v3.19.1
> 
> $ sudo btrfs fi show
> Label: 'roms03'  uuid: b0025417-4045-4c63-a432-0625b7cc41ea
> 	Total devices 4 FS bytes used 2.67TiB
> 	devid    1 size 1.36TiB used 1.36TiB path /dev/sdz
> 	devid    3 size 1.36TiB used 1.36TiB path /dev/sdaa
> 	devid    4 size 1.36TiB used 1.36TiB path /dev/sdab
> 	*** Some devices missing
> 
> This pool is a btrfsraid6 pool
> 
> when trying to mount I get:
> 
> $ sudo mount -t btrfs -o recovery,ro /dev/sdaa /mnt/roms03
> mount: wrong fs type, bad option, bad superblock on /dev/sdaa,
>        missing codepage or helper program, or other error
>        In some cases useful info is found in syslog - try
>        dmesg | tail  or so
> 
> $ dmesg -T|tail
> [Mon May  4 08:35:08 2015] BTRFS info (device sdz): enabling auto recovery
> [Mon May  4 08:35:08 2015] BTRFS info (device sdz): disk space caching is 
> enabled
> [Mon May  4 08:35:08 2015] BTRFS: has skinny extents
> [Mon May  4 08:35:08 2015] BTRFS: failed to read chunk tree on sdz
> [Mon May  4 08:35:08 2015] BTRFS: open_ctree failed
> 
> What could I try to see if I can mount this pool and gain access to the 
> data?

A disk is missing, in this case you should use the "degraded" mount option:

mount -o degraded /dev/sdaa /mnt/roms03



> 
> While I have a backup of the data, next time I may not, and I am trying 
> to learn how to go about. 
> 
> 
> --
> 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
> 


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  reply	other threads:[~2015-05-04 21:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 15:44 [REQ] Help to gain access to btrfsraid6 pool that won't mount TheJay
2015-05-04 21:25 ` Goffredo Baroncelli [this message]
2015-05-04 21:36   ` TheJay
2015-05-05  6:52     ` Chris Murphy
2015-05-05  7:28       ` TheJay
2015-05-05  6:48 ` Chris Murphy
2015-05-05  7:30   ` TheJay
2015-05-06 11:55 ` Duncan
2015-05-06 16:45   ` TheJay
2015-05-06 17:47   ` TheJay

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=5547E3BF.4090901@inwind.it \
    --to=kreijack@inwind.it \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=obiwantje@gmail.com \
    /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).