@timmins
Because things like that only occurred during OOM conditions and never any time
else. Including never during much higher I/O loads. I'm also quite certain it
wasn't limited to sdb, but I haven't let such an OOM condition occur in a long
while, this being one of the reasons.
--
You
Apols for resurrecting an ancient topic, wondering what makes you
suspect this is related to a low memory condition rather than a hardware
problem (drive not responding to the SATA write)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Last occurance happened with 5.4.0-29-generic on Ubuntu 20.04 LTS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1868189
Title:
Low memory situations result in root partition being
I'm still encountering this once a month or so. It's really awful.
How do I make sure that the kernel **always** has enough memory for
buffers and drivers?
It is absolutely inane that a chrome tab can ever cause filesystem
corruption.
** Also affects: linux
Importance: Undecided
** Description changed:
Instead of killing something with a high niceness low memory situations
seem to hang something super-ultra-so-very vital, writes fail and the
root partition is remounted read-only. After that systemd-journald
starts stupidly spamming and earlier logs are rendered
I can't run this command because permanent logging stops and temporary
logging is flooded by systemd.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1868189
Title:
Low memory situations result in root partition being remounted read-
only
7 matches
Mail list logo
