linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Hérikz Nawarro" <herikz.nawarro@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Recover data from damage disk in "array"
Date: Sun, 24 Jan 2021 22:48:37 -0300	[thread overview]
Message-ID: <CAD6NJSxU34_4ygnrqGXmhbMO-wN=rWyxuVuUprP+_bFcNO6b9w@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtRndODgwdnLC6L6Mg7kfO2xEv+wmLfuYsx=kZ0rk8EKgQ@mail.gmail.com>

> I'm not sure what you mean by isolate, or what's meant by recover all
> data. To recover all data on all four disks suggests replicating all
> of it to another file system - i.e. backup, rsync, snapshot(s) +
> send/receive.

I mean, dd the disk to a file and copy the data, before replacing the
broken disk.

> Are there any kernel messages reporting btrfs problems with this file
> system? That should be resolved as a priority before anything else.

No, the fs is fine and i stopped using it when the disk port broke.

> Also, DUP metadata for multiple device btrfs is suboptimal. It's a
> single point of failure. I suggest converting to raid1 metadata so the
> file system can correct for drive specific problems/bugs by getting a
> good copy from another drive. If it's the case DUP metadata is on the
> drive with the bad sata cable, that could easily result in loss or
> corruption of both copies of metadata and the whole file system can
> implode.

I'll try to convert the whole fs as soon as I get a new disk for replacement.

Em sáb., 23 de jan. de 2021 às 03:29, Chris Murphy
<lists@colorremedies.com> escreveu:
>
> On Mon, Jan 18, 2021 at 5:02 PM Hérikz Nawarro <herikz.nawarro@gmail.com> wrote:
> >
> > Hello everyone,
> >
> > I got an array of 4 disks with btrfs configured with data single and
> > metadata dup, one disk of this array was plugged with a bad sata cable
> > that broke the plastic part of the data port (the pins still intact),
> > i still can read the disk with an adapter, but there's a way to
> > "isolate" this disk, recover all data and later replace the fault disk
> > in the array with a new one?
>
> I'm not sure what you mean by isolate, or what's meant by recover all
> data. To recover all data on all four disks suggests replicating all
> of it to another file system - i.e. backup, rsync, snapshot(s) +
> send/receive.
>
> Are there any kernel messages reporting btrfs problems with this file
> system? That should be resolved as a priority before anything else.
>
> Also, DUP metadata for multiple device btrfs is suboptimal. It's a
> single point of failure. I suggest converting to raid1 metadata so the
> file system can correct for drive specific problems/bugs by getting a
> good copy from another drive. If it's the case DUP metadata is on the
> drive with the bad sata cable, that could easily result in loss or
> corruption of both copies of metadata and the whole file system can
> implode.
>
> --
> Chris Murphy

  reply	other threads:[~2021-01-25  1:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19  0:00 Recover data from damage disk in "array" Hérikz Nawarro
2021-01-23  6:29 ` Chris Murphy
2021-01-25  1:48   ` Hérikz Nawarro [this message]
2021-01-23 17:27 ` Zygo Blaxell
2021-01-25  1:41   ` Hérikz Nawarro

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='CAD6NJSxU34_4ygnrqGXmhbMO-wN=rWyxuVuUprP+_bFcNO6b9w@mail.gmail.com' \
    --to=herikz.nawarro@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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).