From: George Mitchell <george@chinilu.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: You guys do an amazing job - I am blown away!
Date: Mon, 17 Aug 2015 15:44:11 -0700 [thread overview]
Message-ID: <55D263BB.2020206@chinilu.com> (raw)
Two years ago I installed btrfs across 8 hard drives on my desktop
system with the entire system ending up on btrfs RAID 1. I did all of
this with btrfs-progs-0.20. Since that time I have been dreading
updating my system because of fear that the old btrfs volumes would
become unstable in the process. I was finally driven to update by
otherwise unresolvable security issues. I went from 32bit OS to 64bit
OS with new btrfs-progs 3.19.1. I simply cannot believe that everything
just worked without a hitch. In terms of btrfs the upgrade from what
was then "experimental" to what is now "stable" was totally
transparent. In the past two years I have had zero problems with btrfs
involving multiple TB of data. I really appreciate all that you guys
have done to make btrfs such an amazing file system.
next reply other threads:[~2015-08-17 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 22:44 George Mitchell [this message]
2015-08-18 17:56 ` You guys do an amazing job - I am blown away! Martin
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=55D263BB.2020206@chinilu.com \
--to=george@chinilu.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).