linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Donald Pearson <donaldwhpearson@gmail.com>,
	Hendrik Friedel <hendrik@friedels.name>
Cc: Omar Sandoval <osandov@fb.com>, Hugo Mills <hugo@carfax.org.uk>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: size 2.73TiB used 240.97GiB after balance
Date: Thu, 09 Jul 2015 08:02:56 -0400	[thread overview]
Message-ID: <559E62F0.4060409@gmail.com> (raw)
In-Reply-To: <CAC=t97CoEZgU4+bQXtJGFrgQfUgXdk0XqUBBVd-rQ=VW7bpxAQ@mail.gmail.com>

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

On 2015-07-08 18:16, Donald Pearson wrote:
> Basically I wouldn't trust the drive that's already showing signs of
> failure to survive a dd.  It isn't completely full, so the recover is
> less load.  That's just the way I see it.  But I see your point of
> trying to get drive images now to hedge against failures.
>
> Unfortunately those errors are over my head so hopefully someone else
> has insights.
>
A better option if you want a block level copy would probably be 
ddrescue (it's available in almost every distro in a package of the same 
name), it's designed for recovering as much data as possible from failed 
disks (and gives a much nicer status display than plain old dd).  If you 
do go for a block level copy however, make certain that no more than one 
of the copies is visible to the system at any given time, especially 
when the filesystem is mounted, otherwise things _WILL_ get 
exponentially worse.



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

  reply	other threads:[~2015-07-09 12:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000f4242.05e425492a977c7b@friedels.name>
2015-07-06 22:59 ` size 2.73TiB used 240.97GiB after balance Donald Pearson
2015-07-07  5:42   ` Hendrik Friedel
2015-07-07 13:14     ` Donald Pearson
2015-07-08 18:56       ` Hendrik Friedel
2015-07-08 19:06         ` Donald Pearson
2015-07-08 21:29           ` Hendrik Friedel
2015-07-08 22:16             ` Donald Pearson
2015-07-09 12:02               ` Austin S Hemmelgarn [this message]
2015-07-09 11:59           ` Austin S Hemmelgarn
2015-07-06 19:20 Hendrik Friedel
2015-07-06 19:44 ` Hendrik Friedel
2015-07-06 19:49   ` Hugo Mills
2015-07-06 20:01     ` Donald Pearson
2015-07-06 20:52       ` Omar Sandoval
2015-07-06 21:12         ` Hendrik Friedel
2015-07-06 21:49           ` Donald Pearson

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=559E62F0.4060409@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=donaldwhpearson@gmail.com \
    --cc=hendrik@friedels.name \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=osandov@fb.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).