linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Timothy Normand Miller <theosib@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: So, wipe it out and start over or keep debugging?
Date: Mon, 17 Aug 2015 07:43:15 -0400	[thread overview]
Message-ID: <55D1C8D3.5090501@gmail.com> (raw)
In-Reply-To: <CAK7bmU88ZfLJmFfMiV=q9RjS+=vAWbniu9w6MUTv_xSG+-hj_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 592 bytes --]

On 2015-08-15 17:46, Timothy Normand Miller wrote:
> To those of you who have been helping out with my 4-drive RAID1
> situation, is there anything further we should do to investigate this,
> in case we can uncover any more bugs, or should I just wipe everything
> out and restore from backup?
>
If you need the system back online, then my suggestion would be to use 
btrfs-image to get metadata images of the disks (there's an option to 
clear out private data if need be), and then restore from backup.  That 
way, we still have the problematic images to work with and examine.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]

  reply	other threads:[~2015-08-17 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 21:46 So, wipe it out and start over or keep debugging? Timothy Normand Miller
2015-08-17 11:43 ` Austin S Hemmelgarn [this message]
2015-08-17 18:52   ` Timothy Normand Miller
2015-08-18 11:21     ` Austin S Hemmelgarn
2015-08-18 13:30       ` Timothy Normand Miller
2015-08-18 15:10         ` Timothy Normand Miller
2015-08-18 15:56           ` Austin S Hemmelgarn
2015-08-18 21:09       ` Chris Murphy
2015-08-18 21:10         ` Timothy Normand Miller
2015-08-20 11:35         ` Austin S Hemmelgarn

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=55D1C8D3.5090501@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=theosib@gmail.com \
    /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).