From: Hugo Mills <hugo@carfax.org.uk>
To: Daniel Pocock <daniel@pocock.com.au>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-tools in Debian squeeze-backports?
Date: Mon, 2 Jan 2012 14:43:40 +0000 [thread overview]
Message-ID: <20120102144340.GA21476@carfax.org.uk> (raw)
In-Reply-To: <4F01BF5D.2070801@pocock.com.au>
[-- Attachment #1: Type: text/plain, Size: 2362 bytes --]
On Mon, Jan 02, 2012 at 03:29:49PM +0100, Daniel Pocock wrote:
> These are the btrfs-tools versions on Debian:
>
> squeeze:
> kernel: 2.6.32
> tools: 0.19+20100601-3
>
> squeeze-backports:
> kernel: 2.6.39
> tools: nothing (so user ends up with 0.19+20100601-3)
>
> wheezy/testing/sid:
> kernel: 3.1.6-1
> tools: 0.19+20111105-2
>
> Using the 2.6.39 kernel from squeeze-backports,
Don't do that. It's pretty old, and there's been a large number of
fixes in btrfs since then. I would recommend using the very latest
kernel you can -- preferably an -rc series kernel (after -rc3
or so, though), or the latest release kernel.
> do I need a newer btrfs-tools
The only real reason to upgrade your btrfs tools is to get access
to the newer features of the FS.
> and is there a particular reason it is not in squeeze-backports too?
You'll have to ask the backports people about that. The btrfs
developers don't have any control over what ends up in most
distributions.
> Or should I not be trying to use the versions in squeeze at all - should
> I be on testing/wheezy or unstable?
You should definitely be on 3.1 or 3.2 kernel at the moment.
> The Debian btrfs wiki and the regular btrfs wiki don't really suggest a
> good starting point (other than suggesting the btrfs has been in Debian
> since squeeze)
> http://wiki.debian.org/Btrfs
>
> If I try to use the version from testing or unstable, I get this error
> on a squeeze setup:
>
> btrfs-tools depends on e2fslibs (>= 1.41.99); however:
> Version of e2fslibs on system is 1.41.12-4stable1.
In that case, I'd suggest either building from the git source tree
for tools (see the wiki[1] for instructions), or, if you insist on
having .deb packages, doing your own backport:
$ apt-get build-dep btrfs-tools
$ apt-get source -t unstable btrfs-tools
$ cd btrfs-tools-0.19+20111105
$ fakeroot debian/rules
$ sudo dpkg -i ../btrfs-tools-0.19+20111105.deb # This may be a different name
Hugo.
[1] http://btrfs.ipv5.de/index.php?title=Btrfs_source_repositories#Official_repository
--
=== 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
--- Anyone using a computer to generate random numbers is, of ---
course, in a state of sin.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2012-01-02 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 14:29 btrfs-tools in Debian squeeze-backports? Daniel Pocock
2012-01-02 14:43 ` Hugo Mills [this message]
2012-01-02 14:55 ` cwillu
2012-01-02 15:01 ` Daniel Pocock
2012-01-02 15:14 ` Hugo Mills
2012-01-02 16:25 ` (renamed thread) btrfs metrics Daniel Pocock
2012-01-02 16:39 ` Hugo Mills
2012-01-04 11:48 ` Daniel Pocock
2012-01-04 18:46 ` Kok, Auke-jan H
2012-01-05 10:09 ` Daniel Pocock
2015-08-30 12:31 ` (renamed thread) btrfs metrics, free space reporting Daniel Pocock
2015-08-31 2:03 ` Qu Wenruo
2012-01-04 18:05 ` btrfs-tools in Debian squeeze-backports? Jan Schmidt
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=20120102144340.GA21476@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=daniel@pocock.com.au \
--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).