Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Philip Love <love_phil@emc.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs bug while defragmenting
Date: Wed, 10 Mar 2010 15:58:08 -0500	[thread overview]
Message-ID: <20100310205808.GG4611@think> (raw)
In-Reply-To: <8C229A18-8B01-4F55-A020-659FDD531C35@emc.com>

On Wed, Mar 10, 2010 at 12:47:59PM -0800, Philip Love wrote:
> I obtained a similar error doing a large write to an ext3 filesystem, so there is another problem somewhere. Sorry for the inconvenience.
> Phil--

I was going to ask about memory corruptions because I couldn't trigger
this bug.  But, I did make a bunch of fixes to the defrag ioctl to fix
problems where it stalls.  So, thanks for sending this report along.

-chris

  reply	other threads:[~2010-03-10 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 18:45 btrfs bug while defragmenting Philip Love
2010-03-09 19:25 ` Chris Mason
2010-03-09 20:06   ` Philip Love
2010-03-09 20:25     ` Philip Love
2010-03-10 20:47       ` Philip Love
2010-03-10 20:58         ` Chris Mason [this message]
2010-03-09 20:21   ` Philip Love

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=20100310205808.GG4611@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=love_phil@emc.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