From: Chris Mason <chris.mason@oracle.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/file.c:528 on Linux 2.6.31.1
Date: Wed, 7 Oct 2009 11:40:28 -0400 [thread overview]
Message-ID: <20091007154028.GI3757@think> (raw)
In-Reply-To: <fbd9d3990910070835y1247893et7a258bdb6c8c3f0a@mail.gmail.com>
On Wed, Oct 07, 2009 at 04:35:37PM +0100, Stefan Hajnoczi wrote:
> On Wed, Oct 7, 2009 at 4:25 PM, Chris Mason <chris.mason@oracle.com> =
wrote:
> > This oops means that we're trying to insert an extent that already
> > exists. =A0I think it is related to the bug in the file clone ioctl=
that
> > Sage recently fixed. =A0The fix is in the master branch of the
> > btrfs-unstable tree.
>=20
> Thanks for explaining this. How can I track when this hits vanilla l=
inux-2.6?
It is already included in 2.6.32-rc1. The master branch of the btrfs
unstable tree is currently based on 2.6.31, so you can just pull it int=
o
a 2.6.31 kernel and you'll get all of the current fixes.
>=20
> > So, I'd say step one is to make a backup of this data.
> >
> > Are you able to figure out which of the files is being written at t=
he
> > time of the oops? =A0If not we can easily add a message to help nai=
l it
> > down.
> >
> > Either way, I'd copy the file that is triggering the problem to a n=
ew
> > file and delete the old one.
>=20
> The data wasn't critical, for now I have switched back to ext3. I
> really like the COW copy feature so I intend to get back on btrfs whe=
n
> I have time to rebuild a kernel with the fix in it.
Ok great. Please let us know if you're able to trigger it again.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-07 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 10:34 kernel BUG at fs/btrfs/file.c:528 on Linux 2.6.31.1 Stefan Hajnoczi
2009-10-07 15:25 ` Chris Mason
2009-10-07 15:35 ` Stefan Hajnoczi
2009-10-07 15:40 ` Chris Mason [this message]
2009-10-07 16:00 ` Stefan Hajnoczi
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=20091007154028.GI3757@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.