On Jan 25, 2014, at 2:47 PM, Dan Merillat <dan.meril...@gmail.com> wrote:
> [ 1219.366168] ntpd invoked oom-killer: gfp_mask=0x201da, order=0, > oom_score_adj=0 > [ 1219.366270] CPU: 1 PID: 5479 Comm: ntpd Not tainted 3.12.8-00848-g97f15f1 > #2 This and the whole call track don't have anything in it that's implicating btrfs or vfs. > > [ 1219.377263] Free swap = 0kB > [ 1219.377320] Total swap = 0kB No swap? > > [ 1219.428330] [ pid ] uid tgid total_vm rss nr_ptes swapents > oom_score_adj name > [ 1219.432471] [ 5383] 103 5383 138079 16199 74 0 > 0 mysqld > > [ 1219.435805] Out of memory: Kill process 5383 (mysqld) score 16 or > sacrifice child > [ 1219.435874] Killed process 5383 (mysqld) total-vm:552316kB, > anon-rss:64576kB, file-rss:220kB It sounds like mysqld is hogging memory for whatever reason, and in the runaway there's no swap to fall back on so things start imploding, which who knows maybe it cause some file system corruption in the process or once the system had to be force quit. Off hand to me it doesn't seem to be directly related to Btrfs. Try reproducing without running the things implicated in this event: ntpd, mysqld. Chris Murphy -- 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
