All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: data DUP
Date: Sun, 28 Apr 2013 01:29:13 -0700	[thread overview]
Message-ID: <klimkl$smn$1@ger.gmane.org> (raw)
In-Reply-To: <kli302$pit$1@ger.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 27/04/13 19:53, Alex Elsayed wrote:
> When using btrfs, run a recent kernel :P.

Every software developer says that of what they produce.  Newer is almost
always better in many different axes.

> Honestly, even leaving aside the lack of backporting, there are other 
> benefits to a recent kernel - things like cross-subvolume reflinks,
> btrfs device replace support being far more efficient than 
> add/balance/remove/balance, and a bunch more.

Those are all "features", none of which I use or have had to use yet.

If it will make you feel better I did upgrade some systems today to the
most recent Ubuntu release which meant going from kernel 3.5 to 3.8.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlF83dUACgkQmOOfHg372QQeDACgz0oBnrYeg6fO5tFxUy9qonE9
HYIAoJWjT8z2sJ356YAph1NAyLKhcEBz
=ySAg
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-04-28  8:29 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
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 [this message]
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='klimkl$smn$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.