Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Calvin Walton <calvin.walton@kepstin.ca>,
	"BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Another defrag question
Date: Thu, 21 Feb 2013 16:38:44 +0000	[thread overview]
Message-ID: <20130221163844.GD14283@carfax.org.uk> (raw)
In-Reply-To: <512644DA.3050409@petaramesh.org>

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

On Thu, Feb 21, 2013 at 05:01:30PM +0100, Swâmi Petaramesh wrote:
> Le 21/02/2013 16:54, Calvin Walton a écrit :
> > You really should upgrade your kernel, however. 3.5.0 is rather old in
> > btrfs-years! Lots of fixes have gone into newer kernels.
> 
> Hi Calvin,
> 
> I expect Ubuntu 13.04 to come with kernel 3.7 in April. Having Ubuntu
> kernel upgrades every 6 months (and several machines), I try to stick as
> much as I can to my distro's kernel. I'm no developper myself and can
> hardly consider that the kernel that came with the latest distro 4
> months ago is actually _that_ old... So I'll live with it for 2 more
> months - unless I'm pretty sure that upgrading to some more recent
> kernel than the one that Ubuntu 13.04 will have would give me huge speed
> improvements or features I need much - (and I assume that being able to

   3.7 is quite a bit faster.

   Plus, if something does go wrong with your FS, and you're running
an older kernel, you'll get limited amounts of sympathy, because quite
a lot of the problems people encounter with older kernels have already
been fixed in newer ones.

   Finally, Ubuntu publish the latest kernels in a PPA[1], so there's
not really much excuse for not keeping up with them.

> defrag, with my snapshots, would be a good reason for me...)

   Hugo.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
               --- Nostalgia isn't what it used to be. ---               

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2013-02-21 16:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 15:46 Another defrag question Swâmi Petaramesh
2013-02-21 15:50 ` Liu Bo
2013-02-21 15:55   ` Swâmi Petaramesh
2013-02-21 15:54 ` Calvin Walton
2013-02-21 16:01   ` Swâmi Petaramesh
2013-02-21 16:09     ` Blair Zajac
2013-02-21 16:38     ` Hugo Mills [this message]
2013-02-21 17:03       ` Swâmi Petaramesh
2013-02-21 17:25         ` Hugo Mills
2013-02-21 17:47           ` Swâmi Petaramesh
2013-02-21 20:46             ` Hugo Mills
2013-02-21 20:58             ` Bardur Arantsson
2013-02-21 21:56               ` David Sterba
2013-02-22  5:55                 ` Bardur Arantsson
2013-02-21 21:31             ` Johannes Hirte

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=20130221163844.GD14283@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=calvin.walton@kepstin.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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