From: Zack Coffey <tech42.clickwir@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: RAID1 fails to recover chunk tree
Date: Thu, 30 Oct 2014 09:30:46 -0400 [thread overview]
Message-ID: <54523D86.5040906@gmail.com> (raw)
In-Reply-To: <54517338.7090606@pobox.com>
Rob, That second drive was immediately put to use elsewhere. I figured
having only the metadata on that drive, it wouldn't matter. The data
stayed single and wasn't part of the second drive, only the metadata
was. I must not be capable of understanding why that wouldn't work.
I thought all I was doing was removing a duplication of metadata and the
worst I would see is a message complaining about a drive missing. Never
thought the data or access to it could be compromised in what seemed to
be a simple situation.
Anand, I get the same output with mount -o recovery,ro.
On 10/29/2014 7:07 PM, Robert White wrote:
> On 10/29/2014 03:26 PM, Robert White wrote:
>> On 10/28/2014 01:32 PM, Zack Coffey wrote:
>>> Made a RAID1 with another drive of just the metadata. Was in
>>> that state for less than 12 hours-ish, removed the second drive and
>>> now cannot get to any data on the original drive. Data remained single
>>> while only metadata was RAID1.
>>
>> I don't know all the details but I would _never_ suspect the action you
>> described to _not_ hose up the file system.
>> You need to put the second drive back in and then coerce all the data
>> back to the first drive. "btrfs device delete" is what you want. You
>> _may_ need to switch the metadata back to "single" before the delete.
>>
>> --Rob.
>>
>
> P.S. I am/was assuming you said "removed the second drive" in the
> normal sense of disconnecting and removing, as opposed to the semantic
> action of deleting the device element.
>
> If you did do the btrfs delete, you might have needed to do a "btrfs
> filesystem sync" to make sure that all the transactions involved in
> the delete were finished and flushed to disk.
>
> Either way, physically reattaching "the second drive" is your first
> step; presuming again that you haven't destroyed the partition or
> re-used the drive etc. If the partition will mount once the second
> drive is in place, do the delete operation (if you didn't) and then
> the sync (to make sure that everything has finished migrating etc).
> Then you should be able to re-remove the physical drive.
>
> If you already did the delete and sync as part of what you meant by
> "remove" then sorry for the interruption of your misery. 8-)
>
next prev parent reply other threads:[~2014-10-30 13:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 20:32 RAID1 fails to recover chunk tree Zack Coffey
2014-10-29 3:55 ` Anand Jain
2014-10-29 19:32 ` Zack Coffey
2014-10-30 3:33 ` Anand Jain
2014-10-29 22:26 ` Robert White
2014-10-29 23:07 ` Robert White
2014-10-30 13:30 ` Zack Coffey [this message]
2014-10-30 15:23 ` Zygo Blaxell
2014-10-30 18:04 ` Chris Murphy
2014-10-31 1:27 ` Duncan
2014-10-31 2:09 ` Chris Murphy
2014-11-02 4:26 ` Robert White
2014-11-02 8:48 ` Roman Mamedov
2014-11-02 11:08 ` Robert White
2014-11-03 6:52 ` Duncan
2014-11-03 8:00 ` Duncan
2014-10-31 8:35 ` Robert White
2014-10-31 12:15 ` Zack Coffey
2014-11-02 4:19 ` Robert White
-- strict thread matches above, loose matches on Subject: below --
2014-10-28 20:18 Zack Coffey
2014-10-27 19:01 Zack Coffey
2014-10-15 21:09 Zack Coffey
2014-10-15 15:42 Zack Coffey
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=54523D86.5040906@gmail.com \
--to=tech42.clickwir@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