public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: Steven Pratt <slpratt@austin.ibm.com>
Subject: Re: Btrfs experimental branch rebased
Date: Thu, 19 Feb 2009 15:26:55 -0500	[thread overview]
Message-ID: <1235075215.28724.45.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1234969860.23031.18.camel@think.oraclecorp.com>

On Wed, 2009-02-18 at 10:11 -0500, Chris Mason wrote:
> Hello everyone,
> 
> My experimental performance fixes would occasionally trigger corruptions
> under load, so I've folded an incremental fix back in and rebased the
> experimental branch.  This was done to prevent git bisects later on from
> landing on the bad commit and corrupting some poor tester's FS.
> 

This seems to be a daily operation, which isn't too surprising because
right now I'm trying to use the experimental branch as a way to
integrate Josef's work and mine frequently.

Today's rebase includes some crucial fixes for my delayed reference
modifications, including crash fixes during btrfs-vol -b.

I've got Josef's latest enospc patches, and I reordered them before the
more experimental performance updates.

The goal is to get the enospc work stable for 2.6.29-rc, and pull those
over to the main branch.

-chris



  reply	other threads:[~2009-02-19 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 15:11 Btrfs experimental branch rebased Chris Mason
2009-02-19 20:26 ` Chris Mason [this message]
2009-02-21 21:44 ` Steven Pratt

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=1235075215.28724.45.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=slpratt@austin.ibm.com \
    /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