From: laie <laie@halifax.rwth-aachen.de>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: destroyed disk in btrfs raid
Date: Thu, 22 May 2014 00:25:56 +0200 [thread overview]
Message-ID: <fc289ec4d8084eaf5ad05c34f5b4f64f@halifax.rwth-aachen.de> (raw)
In-Reply-To: <cabdc599be0699996dc148954aff77dd@halifax.rwth-aachen.de>
On 2014-05-14 23:44, laie wrote:
> On 2014-05-14 20:44, Hugo Mills wrote:
>> On Wed, May 14, 2014 at 08:43:41PM +0200, laie wrote:
>>> On 2014-05-11 16:19, Hugo Mills wrote:
>>> >On Tue, May 13, 2014 at 10:16:59AM +0200, laie wrote:
>>> >>On 2014-05-09 20:01, Hugo Mills wrote:
>>> >>>On Fri, May 09, 2014 at 06:58:27PM +0100, Hugo Mills wrote:
>>> >>>>On Fri, May 09, 2014 at 08:02:45PM +0200, laie wrote:
>>> >>>>> 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.
>>> >>>>
>>> >>>> Simple solution: cat every file to /dev/null, and see which ones
>>> >>>>fail with an I/O error. With RAID-0 data, losing a device is going to
>>> >>>>damage most files, though, so don't necessarily expect much to survive.
>>>
>>> I finished building the List, about 40% of the Data is gone. So far
>>> so good.
>>>
>>> As next step I planned to delete these files. This is not possible
>>> because
>>> I'm not able to mount the fs r/w.
>>>
>>> btrfs: allowing degraded mounts
>>> btrfs: bdev /dev/mapper/luks-0 errs: wr 37519, rd 32783, flush 0,
>>> corrupt 0,
>>> gen 0
>>> Btrfs: too many missing devices, writeable mount is not allowed
>>> btrfs: open_ctree failed
>>>
>>> Is it correct remove the missing device now:
>>>
>>> btrfs device delete missing /mnt
>>>
>>> Or do I have to add the replacement first?
>>
>> You'd have to mount r/w before you can add a new disk. :)
>>
>> You should be able to mount r/w using the -o degraded mount option.
>
> The error above is occurs when I try to mount with
>
> mount -o degraded source target
>
> only
>
> mount -o degraded,ro source target
>
> works.
I'm still stuck here, does anybody have an idea how its possible to get
this filesystem to r/w mode?
The only solution I can think of is to copy the undamaged Data to a new
filesystem. I don't like to do that.
prev parent reply other threads:[~2014-05-21 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 18:02 destroyed disk in btrfs raid laie
2014-05-09 17:58 ` 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 [this message]
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=fc289ec4d8084eaf5ad05c34f5b4f64f@halifax.rwth-aachen.de \
--to=laie@halifax.rwth-aachen.de \
--cc=hugo@carfax.org.uk \
--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).