linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Pocock <daniel@pocock.com.au>
To: cwillu <cwillu@cwillu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-tools in Debian squeeze-backports?
Date: Mon, 02 Jan 2012 16:01:48 +0100	[thread overview]
Message-ID: <4F01C6DC.3040609@pocock.com.au> (raw)
In-Reply-To: <CAE5mzviX5kJ70nG3bLPwE7E3ZjmdQvsKNUbs6XXqVhs+MEeSXw@mail.gmail.com>


> 
> Note that you really want to be running the latest kernel possible if
> using btrfs;  since 2.6.39 there have been several major performance
> fixes, stability fixes, crash-corruption fixes, which users did hit on
> a somewhat regular basis.  Btrfs is not yet stable for the typical
> user who just wants things to work, even when things don't.  I don't
> know of any major distros that offer support services for btrfs
> filesystems, for instance.


I'm not planning to run my whole system on btrfs just yet - but I was
keen to start running one or two test filesystems on a server that I
currently have running Debian squeeze.  Everything else on the server
has to remain as-is if possible.

Thanks for the feedback - I will start looking into the newer kernels
and see if I can use one of them with squeeze, or maybe I will just set
up a VM for btrfs

One thing I've already noticed in 2.6.39 (and both versions of the
tools) is that df results are misleading.  E.g. if I run regular df (not
btrfs fi df), I am seeing the same amount of available space for all
filesystems.  Is there currently a way to see space used by each
subvolume and snapshot and which kernel and tools versions might be needed?


  reply	other threads:[~2012-01-02 15:01 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
2012-01-02 14:55 ` cwillu
2012-01-02 15:01   ` Daniel Pocock [this message]
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=4F01C6DC.3040609@pocock.com.au \
    --to=daniel@pocock.com.au \
    --cc=cwillu@cwillu.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 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).