[lvm-devel] lvm and locales memory issue

Alasdair G Kergon agk at redhat.com
Mon Feb 22 18:51:00 UTC 2010


On Mon, Feb 22, 2010 at 07:23:01PM +0100, Jakub Jelinek wrote:
> That's a bad idea.
 
So we're still no closer to a solution.

So far the only realistic workaround I can think of for Fedora is:

  At lvm startup, check the size of the locale-archive file and the amount of
  memory on the system.  If it looks critical, issue a warning and disable
  locale-setting in LVM.

(Which other distros are affected as well as Fedora/RHEL/CentOS?)

This workaround still does not address the fundamental problem:
glibc is holding open a large mmaped file on behalf of the process and
seemingly offering no way for the process to instruct it to close it without
exiting.

Alasdair




More information about the lvm-devel mailing list