Date: Fri, 14 Sep 2012 01:06:47 GMT From: Ian Jacobi <pipian@pipian.com> To: freebsd-gnats-submit@FreeBSD.org Subject: ia64/171626: tmpfs should be noisier when the requested size cannot be allocated Message-ID: <201209140106.q8E16lB0071368@red.freebsd.org> Resent-Message-ID: <201209140110.q8E1AGMn071476@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 171626 >Category: ia64 >Synopsis: tmpfs should be noisier when the requested size cannot be allocated >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ia64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 14 01:10:15 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Ian Jacobi >Release: 9.0-STABLE >Organization: >Environment: FreeBSD urd 9.0-STABLE FreeBSD 9.0-STABLE #6: Sat Feb 18 18:46:10 EST 2012 pipian@urd:/usr/obj/usr/src/sys/URD amd64 >Description: Although the tmpfs man page states that when the size parameter specified for a tmpfs mount is "larger than SIZE_MAX - PAGE_SIZE... the available amount of memory (including main memory and swap space) will be used." there is no indication logged in dmesg when this is the case, making it difficult to determine why a mounted tmpfs system may have been allocated a smaller size than expected when memory is low. tmpfs should be noisier and print out a warning to dmesg about low available memory when the requested size cannot be allocated. >How-To-Repeat: Attempt to allocate more space to a tmpfs mount than is available in free RAM: mount -t tmpfs -o rw,noauto,size=2684354560 tmpfs /tmp (when available free RAM is less than 2.5GB) >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209140106.q8E16lB0071368>