Hi, Em Qui, 2016-09-01 às 21:11 +0200, Richard Brown escreveu:
What 'builds' are you doing? Why are you doing them on btrfs? Would it make more sense to do them in a subvolume and therefore immunise yourself entirely from the snapshotting of the root subvolume and the quota there?
I'm doing local builds using `osc` before sending them to OBS. This builds are being doing inside a jail directory within my /home. Notice that /home is indeed a subvolume. Also, if you haven't followed the entire issue, I just found a statistical coupling between the problem and local builds. There were many other occurrences in which I saw the ENOSPC while just browsing or after an idle period.
Would it make more sense to use XFS for your non-system data, like SUSE recommend, like openSUSE implements by default and I would also recommend?
This is a problem. My data stays in a separated EXT4 partition. I do not like to put my sensible data inside /home. Hence, /home, for me, it is just a part of the system in which I can delete if something goes wrong after an update due to changes in configuration files. Anyway, I pretty sure that the problem is not related to /home being BTRFS or whatever. Since I moved my jail directory to the EXT4 partition and the problem was not gone. Actually, as Matthias told me, `osc build` downloads a lot of files and put them in /var/cache, which can also be triggering the problem. Conclusion: as of now, we have no idea what triggers the problem, but we have a good evidence that an unstable feature, enabled by default in Tumbleweed, is causing it.
I'd like to know where you and Chris get the idea that the Tumbleweed kernel has absolutely anything to do with the Leap kernel.
I did not get the idea, there was an 'if' in my sentence.
So, while I appreciate your experience with Tumbleweed may have you concerned, your testing on Tumbleweed is invalid in the context of Leap 42.2.
Ok, I'm glad to see that Leap 42.2 does not have this problem, but Tumbleweed has and we have to discuss it.
I would request you use the opportunity of the Beta to test the Beta, and if bugs are present, file them in bugzilla.opensuse.org against the Beta.
Unfortunately it is not possible. This is a production machine and I could not figured out an easy way to trigger the problem. Hence, I do not have the time to test anything here. In my personal laptop, I have never faced this problem so far, but the hardware configuration and usage are completely different. Regards, Ronan Arraes -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org