Date: Fri, 14 Feb 2020 07:54:06 -0500 From: Robert Huff <roberthuff@rcn.com> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-questions@freebsd.org Subject: Re: some questions about disk partitioning and filesystems and booting Message-ID: <24134.39022.519866.759080@jerusalem.litteratus.org> In-Reply-To: <20200214121003.GB39057@bastion.zyxst.net> References: <20200213150229.GC14144@bastion.zyxst.net> <CAEJNuHxrVPfU_TB35AEXaq0QdM=p-v0rnuZWtmAgQdm_KRMNTw@mail.gmail.com> <20200213155256.GD14144@bastion.zyxst.net> <1090523a-377c-9412-5db1-38e825e35956@mm.st> <20200214121003.GB39057@bastion.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
tech-lists writes: > On Thu, Feb 13, 2020 at 07:06:54PM +0300, yp@mm.st wrote: > >Now this is something I wanted to ask as well, as I didn't find > >anything really describing what needs to be done for large (not really > >so this days, 32 and higher) RAM systems -- I have a system with 64GB > >RAM and adding a 64GB swap partition makes system unhappy (I don't > >remember the exact message). With minidumps and all, what size it > >should be so that dump is guaranteed to be saved? > > A while ago I tried this (one big swap partition) and experienced the same. > This is why I went with several swap partitions. I think the maximum swap as a > partition is 32GB and I'm guessing the reason it's like that is down to > some variable buried in the code. _If_ that's true, then it's a bug and needs to be fixed. The folks posting here may not need it ... but I find it hard to imagine various organizations that use FreeBSD (or would like to) on hardcore server hardware wouldn't find that a substantial liability. While this may be more suited to hackers@: can anyone here confirm there is an encoded limit on swap space? Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?24134.39022.519866.759080>