linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: You guys do an amazing job - I am blown away!
Date: Tue, 18 Aug 2015 18:56:21 +0100	[thread overview]
Message-ID: <mqvrk5$hh9$1@ger.gmane.org> (raw)
In-Reply-To: <55D263BB.2020206@chinilu.com>

George,

Always good to see the occasional very positive feedback.

(Even from a non-developer such as myself! :-) )


I've been using various versions of btrfs on both test and production
systems for some time now. Always looks to be spectacular for the care
for backwards compatibility/safety included.

Never done a 32-bit -> 64-bit jump myself but there have been quite a
few leaps made on various hardware/software setups and all without a
hitch keeping the btrfs in place in-situ. Very much preferred compared
to the chore of instead having to read-and-rewrite multiple TBytes of data!


And all still 'experimental'... ;-)

Carry on the good developments!

Regards,
Martin



On 17/08/15 23:44, George Mitchell wrote:
> 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.




      reply	other threads:[~2015-08-18 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 22:44 You guys do an amazing job - I am blown away! George Mitchell
2015-08-18 17:56 ` Martin [this message]

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='mqvrk5$hh9$1@ger.gmane.org' \
    --to=m_btrfs@ml1.co.uk \
    --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).