On Sat, Oct 03, 2009 at 05:55:32PM -0400, Josef Bacik wrote: > On Sat, Oct 03, 2009 at 01:21:09PM +0100, Hugo Mills wrote: > > I've just had the following on my home server. I believe that it's > > btrfs that's responsible, as the machine wasn't doing much other than > > reading/writing on a btrfs filesystem. The process that was doing so > > is now stuck in D+ state, and can't be killed. The timing of the oops > > at the end is also suggestive of being involved in the same incident. > > This is the only btrfs filesystem on the machine. > > > > Patches have gone to Linus to fix the enospc problems. You can try running the > enospc branch of Chris's git tree and it should behave better for you. Thanks, The right tree for this is the master branch of btrfs-unstable for 2.6.31. -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
