Bug 171626 - [tmpfs] tmpfs should be noisier when the requested size cannot be allocated
Summary: [tmpfs] tmpfs should be noisier when the requested size cannot be allocated
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.0-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-14 02:10 UTC by Ian Jacobi
Modified: 2022-01-17 01:30 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Jacobi 2012-09-14 02:10:15 UTC 
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)
Comment 1 Marcel Moolenaar freebsd_committer freebsd_triage 2012-09-25 23:04:08 UTC 
Responsible Changed
From-To: freebsd-ia64->freebsd-amd64

Change category to match environment.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2012-10-08 04:21:50 UTC 
Responsible Changed
From-To: freebsd-amd64->freebsd-fs

reclassify.
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:40 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped