Hey guys,
I believe I have seen a OOM situations reported on the ML and IRC
recently, both of
which are believed to be unrelated to btrfs, which this case is probably
as well; I just
want to provide my dmesg here anyway in case it turns out to be related
to btrfs
nonetheless.
The following is a OOM situation with a headless Ubuntu 16.04.02 LTS
server running
linux 4.8, while copying a lot of files from a broken btrfs FS (thread
"BTRFS
critical: corrupt leaf, slot offset bad; then read-only") to a external
USB3.0 with
btrfs as well.
The box has 16GB of RAM, but this (XEN dom0) is limited to 10 of the
16GB of physical
RAM.
We can see that the OOM killer is pretty desperate and basically kills a
lot of
innocent userspace processes, including systemd, sshd, bash, and some
others.
Not saying this has to be investigated, just keep this dmesg in mind in
case you see
similar reports.
Box is still running for the next 24 hours in case anyone has
troubleshooting
suggesting, but the OOM condition pretty much cleared:
~$ free -m
total used free shared buff/cache
available
Mem: 9956 87 8625 3 1243 9664
Swap: 10239 23 10216
~$ uname -a
Linux srv1-dom0 4.8.0-39-generic #42~16.04.1-Ubuntu SMP Mon Feb 20
15:06:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
~$ btrfs version
btrfs-progs v4.4
~$
dmesg pastebin:
http://pastebin.com/raw/yTPh19m4
Omitted inline dmesg as it doesn't fi in 100KB.
cheers,
lukas
--
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
