From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Calvin Walton <calvin.walton@kepstin.ca>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Another defrag question
Date: Thu, 21 Feb 2013 17:01:30 +0100 [thread overview]
Message-ID: <512644DA.3050409@petaramesh.org> (raw)
In-Reply-To: <1361462073.18057.23.camel@cwalton-XPS-8300>
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
defrag, with my snapshots, would be a good reason for me...)
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next prev parent reply other threads:[~2013-02-21 16:01 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 [this message]
2013-02-21 16:09 ` Blair Zajac
2013-02-21 16:38 ` Hugo Mills
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=512644DA.3050409@petaramesh.org \
--to=swami@petaramesh.org \
--cc=calvin.walton@kepstin.ca \
--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.