From: Roman Mamedov <rm@romanrm.net>
To: Klaus Agnoletti <klaus@agnoletti.dk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: A partially failing disk in raid0 needs replacement
Date: Tue, 14 Nov 2017 19:44:26 +0500 [thread overview]
Message-ID: <20171114194426.07ac4e85@natsu> (raw)
In-Reply-To: <CAFTHvW9=ojuQW0GWRLdy2g4j7DSzT13-=ODrjhjWAq3YMEiszg@mail.gmail.com>
On Tue, 14 Nov 2017 15:09:52 +0100
Klaus Agnoletti <klaus@agnoletti.dk> wrote:
> Hi Roman
>
> I almost understand :-) - however, I need a bit more information:
>
> How do I copy the image file to the 6TB without screwing the existing
> btrfs up when the fs is not mounted? Should I remove it from the raid
> again?
Oh, you already added it to your FS, that's so unfortunate. For my scenario I
assumed have a spare 6TB (or any 2TB+) disk you can use as temporary space.
You could try removing it, but with one of the existing member drives
malfunctioning, I wonder if trying any operation on that FS will cause further
damage. For example if you remove the 6TB one, how do you prevent Btrfs from
using the bad 2TB drive as destination to relocate data from the 6TB drive. Or
use it for one of the metadata mirrors, which will fail to write properly,
leading into transid failures later, etc.
--
With respect,
Roman
next prev parent reply other threads:[~2017-11-14 14:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 8:36 A partially failing disk in raid0 needs replacement Klaus Agnoletti
2017-11-14 12:38 ` Adam Borowski
2017-11-15 2:54 ` Chris Murphy
2017-11-14 12:48 ` Roman Mamedov
2017-11-14 12:58 ` Austin S. Hemmelgarn
2017-11-14 14:09 ` Klaus Agnoletti
2017-11-14 14:44 ` Roman Mamedov [this message]
2017-11-14 15:43 ` Klaus Agnoletti
2017-11-26 9:04 ` Klaus Agnoletti
2017-11-14 14:43 ` Kai Krakow
2017-11-15 2:56 ` Chris Murphy
2017-11-14 12:54 ` Patrik Lundquist
2017-11-14 13:14 ` Austin S. Hemmelgarn
2017-11-14 14:10 ` Klaus Agnoletti
2017-11-15 2:47 ` Chris Murphy
2017-11-29 13:33 ` Klaus Agnoletti
2017-11-29 21:58 ` Chris Murphy
2017-11-30 5:28 ` Klaus Agnoletti
2017-11-30 6:03 ` Chris Murphy
2017-11-30 6:41 ` Klaus Agnoletti
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=20171114194426.07ac4e85@natsu \
--to=rm@romanrm.net \
--cc=klaus@agnoletti.dk \
--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).