From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: klaus.mailinglists@pernau.at
Cc: pgsql-general@postgresql.org
Subject: Re: PANIC: could not flush dirty data: Cannot allocate memory
Date: Tue, 15 Nov 2022 22:17:05 +0100
Message-ID: <Y3QB0aANtLBAjyVc@elch.exwg.net> (raw)
In-Reply-To: <7e02611b56aebc62a0ec25bb39687491@pernau.at>
References: <ec01f7af535c0c38711a317cba2aa310@pernau.at>
<Y3K4+z5fP9mNElMj@elch.exwg.net>
<7e02611b56aebc62a0ec25bb39687491@pernau.at>
## klaus.mailinglists@pernau.at (klaus.mailinglists@pernau.at):
> AFAIU the problem is not related to the memory settings in
> postgresql.conf. It is the kernel that
> for whatever reasons report ENOMEM. Correct?
Correct, there's a ENOMEM from the kernel when writing out data.
> Filesystem is ext4. VM technology is mixed: VMware, KVM and XEN PV.
> Kernel is 5.15.0-52-generic.
I do not suspect the filesystem per se, ext4 is quite common and we
would have heard something about that (but then, someone gotta be
the first reporter?). I would believe that the kernel would raise
a bunch of printks if it hit ENOMEM in the commonly used paths, so
you would see something in dmesg or wherever you collect your kernel
log if it happened where it was expected.
And coming from the other side: does this happen on all the hosts,
or is it limited to one host or one technology? Any uncommon options
on the filesystem or the mount point? Anything which could mess
with your block devices? (I'm expecially thinking "antivirus" because
it's always "0 days since the AV ate a database" and they tend to
raise errors in the weirdest places, which would fit the bill here;
but anythig which is not "commonly in use everywhere" could be a
candidate).
Regards,
Christoph
--
Spare Space
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: cmt@burggraben.net, klaus.mailinglists@pernau.at
Subject: Re: PANIC: could not flush dirty data: Cannot allocate memory
In-Reply-To: <Y3QB0aANtLBAjyVc@elch.exwg.net>
References: <ec01f7af535c0c38711a317cba2aa310@pernau.at> <Y3K4+z5fP9mNElMj@elch.exwg.net> <7e02611b56aebc62a0ec25bb39687491@pernau.at> <Y3QB0aANtLBAjyVc@elch.exwg.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox