linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@Oracle.COM>
To: Chris Samuel <chris@csamuel.org>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: version
Date: Mon, 24 Jan 2011 20:03:24 -0500	[thread overview]
Message-ID: <1295917366-sup-2191@think> (raw)
In-Reply-To: <4D3E012E.4070208@csamuel.org>

Excerpts from Chris Samuel's message of 2011-01-24 17:46:06 -0500:
> On 25/01/11 08:39, Helmut Hullen wrote:
> 
> > Regard the difference between "df" and "btrfs filesystem df".
> 
> I suspect this is fixed in 2.6.38 with the following commit.
> 
> BE WARNED: there are some fairly hairy changes to the pathname
> lookup code to replace the BKL with RCU (not specific to btrfs)
> and so if you are tempted to try it (currently 2.6.38-rc2) only
> do so on a system that you don't care about data on and/or have
> very good incremental backups of which you trust...

Yes, and you can pull in these commits on top of 2.6.37 or 2.6.36 by
pulling in the btrfs-unstable git tree.  But I do agree they should fix
it.

-chris

  reply	other threads:[~2011-01-25  1:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 21:06 btrfs, broken design? Benoît Thiébault
2011-01-20 21:20 ` Chris Mason
2011-01-21  5:25   ` Benoît Thiébault
2011-01-21  6:46     ` Chester
2011-01-21  8:11       ` Benoît Thiébault
2011-01-21  8:21         ` Hubert Kario
2011-01-21  9:54   ` version (was: btrfs, broken design?) Helmut Hullen
2011-01-21 12:21     ` Hugo Mills
2011-01-21 14:10       ` version Helmut Hullen
2011-01-21 14:32     ` version (was: btrfs, broken design?) Diego Calleja
2011-01-21 14:55       ` version Helmut Hullen
2011-01-21 15:12         ` version Hugo Mills
2011-01-21 15:19           ` version Helmut Hullen
2011-01-24  3:20         ` version Chris Samuel
2011-01-24  8:33           ` version Helmut Hullen
2011-01-24 21:14             ` version Johannes Hirte
2011-01-24 21:39               ` version Helmut Hullen
2011-01-24 22:46                 ` version Chris Samuel
2011-01-25  1:03                   ` Chris Mason [this message]
2011-01-25  6:43                   ` version Helmut Hullen
2011-01-25 14:37                   ` version Helmut Hullen
2011-01-27  5:02                     ` 2.6.38-rc2 oops's when rebalancing on different size drives (was Re: version) Chris Samuel
2011-01-27  7:45                     ` version Chris Mason
2011-01-27  8:16                       ` version Helmut Hullen
2011-01-27 13:28                       ` version Helmut Hullen
2011-01-27 13:49                       ` no space left (was: version) Helmut Hullen
2011-01-26 10:13       ` version (was: btrfs, broken design?) Erik Logtenberg
2011-01-26 14:13         ` Diego Calleja

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=1295917366-sup-2191@think \
    --to=chris.mason@oracle.com \
    --cc=chris@csamuel.org \
    --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).