linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Samuel <chris@csamuel.org>
To: Chris Mason <chris.mason@oracle.com>, Avi Kivity <avi@redhat.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs oops (autodefrag related?)
Date: Tue, 13 Mar 2012 11:13:28 +1100	[thread overview]
Message-ID: <201203131113.32951.chris@csamuel.org> (raw)
In-Reply-To: <20120313000435.GH29393@shiny>

[-- Attachment #1: Type: Text/Plain, Size: 708 bytes --]

On Tuesday 13 March 2012 11:04:35 Chris Mason wrote:

> This one was fixed in the 3.3 series.  You can pull from my
> for-linus repo for a commit against 3.2.

Note though that some people are reporting regressions with premature 
ENOSPC in 3.3-rc7, to quote:

# - bisected down to 5500cdb (Btrfs: increase the global block
# reserve estimates). After reverting this one Linus master works
# for me again.

Though after reversion they hit ENOSPC much later (but still 
prematurely).

cheers,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]

  reply	other threads:[~2012-03-13  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 19:32 btrfs oops (autodefrag related?) Avi Kivity
2012-03-13  0:04 ` Chris Mason
2012-03-13  0:13   ` Chris Samuel [this message]
2012-03-13  1:34     ` Chris Samuel
2012-03-13  8:57   ` Avi Kivity

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=201203131113.32951.chris@csamuel.org \
    --to=chris@csamuel.org \
    --cc=avi@redhat.com \
    --cc=chris.mason@oracle.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).