Subject: Re: free space (was /dev) on tmpfs problem
To: None <email@example.com>
From: Matthew Mondor <firstname.lastname@example.org>
Date: 11/15/2005 17:42:55
On Tue, 15 Nov 2005 20:10:02 +0100
Manuel Bouyer <email@example.com> wrote:
> > such that "Capacity" would always be 100% (except again where an option is
> > used to specify the maximum allowed size)?
> > If the number of bytes/blocks in use can be accounted by the FS, wouldn't
> > it be simple to do it this way?
> This may break softwares that tries to see if they have enouth space before
> writing a file.
I thought that tmpfs would mostly be used for /tmp, /dev or other
similar filesystems on which this would not have been an important
If it's also used for more multipurpose use on a specific mountpoint, I
thought at first that it would make sense for the admin to specify an
upper limit there, and thus obtain proper df results, but this has
problems, since we don't want to reserve that memory at mount time.
An allowed upper bound would need to not exceed system constraints, and
those unfortunately dynamically change at runtime. After reflection I
guess we have no choice but to somehow dynamically use actual remaining
resources to evaluate remaining space at runtime like some others have
Note: Please only reply on the list, other mail is blocked by default.
Private messages from your address can be allowed by first asking.