[SOLVED] Virtual Memory limit exhausted at 1TB? malloc/mmap failures even with free memory
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Virtual Memory limit exhausted at 1TB? malloc/mmap failures even with free memory
Curious,
even with ulimit for virtual mem set to unlimited or 0, I get malloc failures after about 1 TB virtual is exhausted, with malloc size > 128kB that should do a private mmap. Disk-supported mmap still seem to work beyond one terabyte.
Anybody encountered similar? Could it be my testing distro is a "desktop" instead of an enterprise version? Many thanks.
24 GB RAM + 36 GB Swap, 1020 GB can be allocated (of course not used). mmap against some 1TB+ disks in raid, malloc fails with ENOMEM after approx 1TB with 0% swap and 30% ram real usage.
Just wondering if anybody has some ideas.
I thought the virtual limit to be 128TB, sometimes 64TB, on Intel distros, not just 1TB.....
I would be suspecting something like control block shortage. Keep an eye on /proc/meminfo and /proc/slabinfo ("cat" them to disk for later perusal).
There is also slabtop which can be handy in "normal" storage shortages, but don't use it when the system (i.e. kernel controlled) storage is in crisis. Your system might just appear to "go away" - maybe for several hours.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.