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@xxxxxxxxxx> wrote: > > This oops means that we're trying to insert an extent that already > > exists. I think it is related to the bug in the file clone ioctl that > > Sage recently fixed. The fix is in the master branch of the > > btrfs-unstable tree. > > Thanks for explaining this. How can I track when this hits vanilla linux-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 into a 2.6.31 kernel and you'll get all of the current fixes. > > > 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 the > > time of the oops? If not we can easily add a message to help nail it > > down. > > > > Either way, I'd copy the file that is triggering the problem to a new > > file and delete the old one. > > 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 when > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
