From: Alexandre Poux <pums974@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: multi-device btrfs with single data mode and disk failure
Date: Thu, 15 Sep 2016 09:44:18 +0200 [thread overview]
Message-ID: <1634818f-ff1d-722c-6d73-747ed7203a13@gmail.com> (raw)
I had a btrfs partition on a 6 disk array without raid (metadata in
raid10, but data in single), and one of the disks just died.
So I lost some of my data, ok, I knew that.
But two question :
*
Is it possible to know (using metadata I suppose) what data I have
lost ?
*
Is it possible to do some king of a "btrfs delete missing" on this
kind of setup, in order to recover access in rw to my other data, or
I must copy all my data on a new partition
I haven't been able to get any answer on google or in the wiki, so I
send here an e-mail, hoping that's the right place. Excuse me, if I'm wrong.
Thank you for any help
(Sorry for my poor english)
uname -a :
Linux Grand-PC 4.7.2-1-ARCH #1 SMP PREEMPT Sat Aug 20 23:02:56 CEST 2016
x86_64 GNU/Linux
btrfs --version :
btrfs-progs v4.7.1
btrfs fi show :
Label: 'Data' uuid: 62db560b-a040-4c64-b613-6e7db033dc4d
Total devices 6 FS bytes used 6.66TiB
devid 1 size 2.53TiB used 2.12TiB path /dev/sdd6
devid 7 size 2.53TiB used 2.12TiB path /dev/sdb6
devid 9 size 262.57GiB used 0.00B path /dev/sde6
devid 11 size 2.53TiB used 2.12TiB path /dev/sdc6
devid 12 size 728.32GiB used 312.03GiB path /dev/sda6
*** Some devices missing
mount -o recovery,ro,degraded /dev/sda6 /Data
relevant part of dmesg :
[ 1828.093704] BTRFS warning (device sda6): 'recovery' is deprecated,
use 'usebackuproot' instead
[ 1828.093708] BTRFS info (device sda6): trying to use backup root at
mount time
[ 1828.093718] BTRFS info (device sda6): allowing degraded mounts
[ 1828.093719] BTRFS info (device sda6): disk space caching is enabled
[ 1828.107763] BTRFS warning (device sda6): devid 8 uuid
950378c0-307c-413d-9805-ab2bb899aa78 missing
btrfs fi df /Data
Data, single: total=6.65TiB, used=6.65TiB
System, RAID1: total=32.00MiB, used=768.00KiB
Metadata, RAID1: total=13.00GiB, used=10.99GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
next reply other threads:[~2016-09-15 7:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 7:44 Alexandre Poux [this message]
2016-09-15 15:38 ` multi-device btrfs with single data mode and disk failure Chris Murphy
2016-09-15 16:30 ` Alexandre Poux
2016-09-15 16:54 ` Chris Murphy
[not found] ` <760be1b7-79b2-a25d-7c60-04ceac1b6e40@gmail.com>
2016-09-15 21:54 ` Chris Murphy
2016-09-19 22:05 ` Alexandre Poux
2016-09-20 17:03 ` Alexandre Poux
2016-09-20 17:54 ` Chris Murphy
2016-09-20 18:19 ` Alexandre Poux
2016-09-20 18:38 ` Chris Murphy
2016-09-20 18:53 ` Alexandre Poux
2016-09-20 19:11 ` Chris Murphy
[not found] ` <4e7ec5eb-7fb6-2d19-f29d-82461e2d0bd2@gmail.com>
2016-09-20 19:46 ` Chris Murphy
2016-09-20 20:18 ` Alexandre Poux
2016-09-20 21:05 ` Alexandre Poux
2016-09-20 21:15 ` Chris Murphy
2016-09-29 12:55 ` Alexandre Poux
2016-09-30 23:46 ` Alexandre Poux
2016-09-20 19:43 ` Austin S. Hemmelgarn
2016-09-20 19:54 ` Alexandre Poux
2016-09-20 20:02 ` Chris Murphy
2016-09-20 19:55 ` Chris Murphy
2016-09-21 11:07 ` Austin S. Hemmelgarn
2016-09-20 20:59 ` Graham Cobb
2016-09-20 18:56 ` Austin S. Hemmelgarn
2016-09-20 19:06 ` Alexandre Poux
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=1634818f-ff1d-722c-6d73-747ed7203a13@gmail.com \
--to=pums974@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 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).