From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: data DUP
Date: Sat, 20 Apr 2013 16:01:32 -0700 [thread overview]
Message-ID: <kkv6o8$9f0$1@ger.gmane.org> (raw)
In-Reply-To: <20130420212311.GO7639@carfax.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 20/04/13 14:23, Hugo Mills wrote:
> You should upgrade anyway -- there's been a number of serious bugs in
> btrfs fixed since then.
13.04 is imminent so I'll pick up a newer kernel as part of that anyway.
(Also Tanglu which I hope to move to intends to use the Ubuntu kernel anyway.)
In any event I am not worried. Bug fixes get backported. The probability
of hitting any serious bug is low (others would likely be victims first)
and worst case I have backups (snapshots, other machines, Google/Dropbox,
DVDs & hard drives at other people's houses etc).
There are two major reasons I switched from ext4. The first is that
everything is online, including adding and removing devices, checking data
integrity etc.
The second is that data not silently lost. I had some bad sectors develop
on ext4 spinning disk and the only way to properly recover was to do
offline checks that would have taken ~ 24 hours! Finding out which
filenames were involved was far too much effort.
My philosophy is that we have machines with billions of processor cycles
per second. They can figure things out for themselves without requiring
me to baby sit them!
I also run btrfs in a variety of configurations - raid0, raid1, sata, usb,
hdd, ssd, single device, multi-device, bare, dmcrypt, machines on all the
time, laptop, frequent suspend/resume, frequent power on/off. I've never
experienced any problems with btrfs and use scrub for reassurance.
Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAlFzHkwACgkQmOOfHg372QSBBwCfYYJQm9l9ts9eWOvZIRUlTCWJ
KsMAoLVsd1fRdV+T7KO7nVVGuFCGYN5a
=Y4by
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-04-20 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 20:17 data DUP Roger Binns
2013-04-20 20:48 ` Hugo Mills
2013-04-20 21:15 ` Roger Binns
2013-04-20 21:23 ` Hugo Mills
2013-04-20 23:01 ` Roger Binns [this message]
2013-04-27 21:40 ` Calvin Walton
2013-04-27 23:29 ` Roger Binns
2013-04-28 2:53 ` Alex Elsayed
2013-04-28 8:29 ` Roger Binns
2013-04-22 13:37 ` 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='kkv6o8$9f0$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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.