linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: laie <laie@halifax.rwth-aachen.de>
To: linux-btrfs@vger.kernel.org
Subject: destroyed disk in btrfs raid
Date: Fri, 09 May 2014 20:02:45 +0200	[thread overview]
Message-ID: <2a45648842c071a8e0d3285541d96c6f@halifax.rwth-aachen.de> (raw)

Hello!

I've some trouble with my btrf filesystem. I've lost one backing raid 
device, it's luks header is overwritten and not restoreable.

The lost disk was recently added. 'btrfs filesystem balace' was running 
for some time, but the new device is the smallest in the set.

Data is stored with Raid0, Metadata with Raid1. Degraded mounting works 
fine.

Now I'm looking for a way to tell btrfs to provide me with a list of the 
corrupted files and delete them afterwards. This would be great, because 
otherwise it would take very long to get the data back from slow 
backups.

Thanks in advance
Max


btrfs --version
Btrfs v3.12

btrfs fi show
Label: userspace  uuid: there is one ;)
         Total devices 3 FS bytes used 27.21TiB
         devid    1 size 21.83TiB used 13.03TiB path /dev/dm-3
         devid    2 size 16.37TiB used 13.01TiB path /dev/dm-2
         devid    3 size 8.19TiB used 4.27TiB path

btrfs fi df /home/
Data, RAID0: total=30.24TiB, used=27.18TiB
System, RAID1: total=32.00MiB, used=1.99MiB
System, single: total=4.00MiB, used=0.00
Metadata, RAID1: total=32.00GiB, used=31.42GiB


             reply	other threads:[~2014-05-09 17:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 18:02 laie [this message]
2014-05-09 17:58 ` destroyed disk in btrfs raid Hugo Mills
2014-05-09 18:01   ` Hugo Mills
2014-05-13  8:16     ` laie
2014-05-11 14:19       ` Hugo Mills
2014-05-14 18:43         ` laie
2014-05-14 18:44           ` Hugo Mills
2014-05-14 21:44             ` laie
2014-05-21 22:25               ` laie

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=2a45648842c071a8e0d3285541d96c6f@halifax.rwth-aachen.de \
    --to=laie@halifax.rwth-aachen.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).