From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Questions about multi-device behavior
Date: Wed, 17 Jul 2013 19:00:24 -0700 [thread overview]
Message-ID: <ks7i7i$9ev$1@ger.gmane.org> (raw)
In-Reply-To: <1860433.azE0Vf7tMy@horus>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 17/07/13 14:24, Florian Lindner wrote:
> metadata ist mirrored on each device, data chunks are scattered more or
> less randomly on one disk.
>
> a) If one disk fails, is there any chance of data recovery? b) If not,
> is there any advantage over a raid0 configuration.
I was using that exact configuration when one disk failed (2 x 2TB Seagate
drives). The data was backed up in multiple ways, a lot of it was in
source control systems and the remainder was generated information.
Essentially the risk was worth taking since nothing would be lost.
One drive gave up mechanically - the controller still worked and it was
fun running SMART tests and having huge amounts of red text show up in
response. The initial symptoms were that various programs crashed or
didn't launch with no diagnostics. That is typical behaviour for Linux
apps when they get I/O errors on reads and writes.
Eventually I figured out the problem, and bought a new 4TB drive to
replace both originals and started recovery. Out of ~750GB of original
data I could recover just over 2GB which represented files whose entire
contents were on the unfailed drive.
Having the metadata duplicated was however immensely helpful and I could
easily get a list of all directories and filenames, and used that to guide
what data I recovered/regenerated/reinstalled/checked out.
Meanwhile the performance improvement by having the data scattered across
both drives was noticeable. I would often see it in iostat roughly evenly
balanced.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlHnTDgACgkQmOOfHg372QSTJwCeI17B4QhstkM4nnO0qOMDB1ae
WfwAoOBu6lBwZ+GyFwnZVGXC5ki7Oge/
=i+YN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-18 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 21:24 Questions about multi-device behavior Florian Lindner
2013-07-17 21:49 ` Chris Murphy
2013-07-18 2:00 ` Roger Binns [this message]
2013-07-18 17:33 ` David Sterba
2013-07-18 20:05 ` Chris Murphy
2013-07-18 21:59 ` Roger Binns
2013-07-18 22:03 ` Hugo Mills
2013-08-02 14:10 ` David Sterba
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='ks7i7i$9ev$1@ger.gmane.org' \
--to=rogerb@rogerbinns.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;
as well as URLs for NNTP newsgroup(s).