On Wed, Jan 23, 2013 at 08:41:25AM +1100, Skender wrote: > The only lines the have anythinf with btrfs are as follows: [...]
That lacks information to analyze the error, so let's try it the usual way. I'm not sure if you can grab the state of free space (via btrfs fi df) from the time it happened, but that would at least say if it was the ENOSPC case. thanks, david -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
