On Thu, Aug 25, 2016 at 9:58 AM, Lutz Vieweg <lvml@xxxxxx> wrote: > On 08/16/2016 01:24 AM, Chris Murphy wrote: >> >> On Mon, Aug 15, 2016 at 5:12 PM, Ronan Chagas <ronisbr@xxxxxxxxx> wrote: >>> >>> It happened again. The computer was completely unusable. The only useful >>> message I saw was this one: >>> >>> http://img.ctrlv.in/img/16/08/16/57b24b0bb2243.jpg >> >> >> Looks similar to this: >> https://lkml.org/lkml/2016/3/28/230 > > > Looks also similar to the subject of the lenghty thread titled > "6TB partition, Data only 2TB - aka When you haven't hit the "usual" > problem" > that started with: >> >> http://www.spinics.net/lists/linux-btrfs/msg50599.html I'm thinking it might be a conflict with the OP doing builds, implies heavy writes, maybe especially heavy metadata based on the large increase in metadata allocation; along with the default on opensuse using snapper to make read only snapshots. That it can't be triggered on demand makes sense, if the build doesn't overlap with snapper making a snapshot of /home. http://www.spinics.net/lists/linux-btrfs/msg52670.html Anyway it's a known problem, I don't think it's fixed still. There's a lot of enospc work in 4.8 so eventually it'll make sense to give it a shot with that kernel. -- Chris Murphy -- 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
