On Fri, 4 Jul 2014 07:24:16 Marc MERLIN wrote: > On Fri, Jul 04, 2014 at 03:23:41PM +0900, Satoru Takeuchi wrote: > > >Is there any correlation between such problems and BTRFS operations such > > >as > > >creating snapshots or running a scrub/balance? > > > > Were you running scrub, Marc? > > Yes, I was due to the other problem I was discussing on the list. I > wanted to know if scrub would find any problem (it did not). > I think I'll now try to read every file of every filesystem to see what > btrfs does (this will take a while, that's around 100 million files). > > But the last times I had this OOM problem with 3.15.1 it was happening > within 6 hours sometimes, and I was not starting scrub every time the > system booted, so scrub may be partially responsible but it's not the > core problem.
It would be a good idea to run a few scrubs and see if this is a repeatable problem. If it's a repeatable problem then it's something to fix regardless of whether it's the only issue you have. > > Marc, do you change > > > > - software and its setting, > > - operations, > > - hardware configuration, > > > > or any other, just before detecting first OOM? > > Those are 3 good questions, I asked myself the same thing. > From what I remember though all I did was going from 3.14 to 3.15. > However this machine has many cronjobs, it does rsyncs to and from > remote systems, it has btrfs send/receive going to and from it, and > snapshots every hour. > Those are not new, but if any of them changed in a small way, I guess > they could trigger bugs. If a scrub can reliably trigger the problem it would be good to test 3.14 for the same behavior. Knowing whether it's a regression would help the developers. > > You have 8GB RAM and there is plenty of swap space. > > Correct. Even without much swap 8G should be a plenty. My main workstation has 4G of RAM and 6G of swap. I almost never use more than 3G of swap because the system becomes so slow as to be almost unusable when swap gets to 4G (Chromium is to blame). However that is for a 120G non-RAID filesystem. Presumably a RAID array will need some more kernel memory and a larger filesystem will also need a little more, but it still shouldn't be that much. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
