From nobody  Thu Sep 18 14:20:04 1997
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA07620;
          Thu, 18 Sep 1997 14:20:04 -0700 (PDT)
Message-Id: <199709182120.OAA07620@hub.freebsd.org>
Date: Thu, 18 Sep 1997 14:20:04 -0700 (PDT)
From: ajhar@noao.edu
To: freebsd-gnats-submit@freebsd.org
Subject: mfs does not mount requested size from /etc/fstab
X-Send-Pr-Version: www-1.0

>Number:         4576
>Category:       misc
>Synopsis:       mfs does not mount requested size from /etc/fstab
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Sep 18 14:30:01 PDT 1997
>Closed-Date:    Sun Apr 26 16:12:48 PDT 1998
>Last-Modified:  Sun Apr 26 16:16:13 PDT 1998
>Originator:     Edward Ajhar
>Release:        FreeBSD-2.2-stable from 1997-09-10
>Organization:
National Optical Astronomy Observatories
>Environment:
FreeBSD husa.tuc.noao.edu 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri Sep 12 11:46:07 MST 1997     ajhar@husa.tuc.noao.edu:/usr/src/sys/compile/HUSA  i386

>Description:
Memory file system when mounted automatically from /etc/fstab does
not yield the size filesystem requested.  It appears that ~32MB is
what you get regardless of what you want, but I have not tried this
for sizes smaller than 32MB.  (Previously, the size was about the
size of the partition [I think].)  This began happening, I believe,
some time in August.


>How-To-Repeat:
If /etc/fstab contains

  /dev/sd0s1b		/tmp		mfs	rw,-s=131072	0	0

a 'df' yields

  Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
  mfs:28          31404        4    28888     0%    /tmp


However, it DOES work to mount a filesystem manually with

   mount -t mfs -o -s=131072 /dev/sd1s1b /mnt

This yields 

   Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
   mfs:288         63567        1    58481     0%    /mnt

although this is not really an acceptable work-around for /tmp.

>Fix:

>Release-Note:
>Audit-Trail:

From: Peter Wemm <peter@spinner.dialix.com.au>
To: ajhar@noao.edu
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: misc/4576: mfs does not mount requested size from /etc/fstab 
Date: Fri, 19 Sep 1997 07:58:39 +0800

 ajhar@noao.edu wrote:
 > >Number:         4576
 > >Category:       misc
 > >Synopsis:       mfs does not mount requested size from /etc/fstab
 [..]
 > >How-To-Repeat:
 > If /etc/fstab contains
 >   /dev/sd0s1b		/tmp		mfs	rw,-s=131072	0	0
 > a 'df' yields
 >   Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 >   mfs:28          31404        4    28888     0%    /tmp
 > 
 > However, it DOES work to mount a filesystem manually with
 >    mount -t mfs -o -s=131072 /dev/sd1s1b /mnt
 > This yields 
 >    Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 >    mfs:288         63567        1    58481     0%    /mnt
 > although this is not really an acceptable work-around for /tmp.
 
 This is a ``bug'' in the default /etc/login.conf settings.  The resource
 limits for 'daemon' are what /etc/rc (and hence the mfs mount at boot) are
 run with. 'daemon' has a datasize limit of 32MB, and mount_mfs goes to a
 fair bit of trouble to fit within it's hard data limit.  I have been 
 thinking of having mount_mfs reset it's hard data limit to infinity if run 
 by root (such as at boot time).  This will get a fssize of what was asked 
 for in spite of the /etc/login.conf settings.  Another fix would be to put 
 some more suitable settings for daemon in login.conf.
 
 Cheers,
 -Peter
 
 

From: "Matthew N. Dodd" <winter@jurai.net>
To: ajhar@noao.edu
Cc: freebsd-gnats-submit@FreeBSD.ORG, GNATS Management <gnats@FreeBSD.ORG>,
        freebsd-bugs@hub.freebsd.org
Subject: Re: misc/4576: mfs does not mount requested size from /etc/fstab
Date: Thu, 18 Sep 1997 22:21:42 -0400 (EDT)

 Sorry, this works for me on a fairly recent 2.2-STABLE system
 
 /dev/sd0s2b     /tmp      mfs     rw,async,nosuid,nodev,-s=131072 0 0
 
 mfs:22          63567     1313    57169     2%    /tmp
 
 
 On Thu, 18 Sep 1997 ajhar@noao.edu wrote:
 
 > 
 > >Number:         4576
 > >Category:       misc
 > >Synopsis:       mfs does not mount requested size from /etc/fstab
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-bugs
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Thu Sep 18 14:30:01 PDT 1997
 > >Last-Modified:
 > >Originator:     Edward Ajhar
 > >Organization:
 > National Optical Astronomy Observatories
 > >Release:        FreeBSD-2.2-stable from 1997-09-10
 > >Environment:
 > FreeBSD husa.tuc.noao.edu 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri Sep 12 11:46:07 MST 1997     ajhar@husa.tuc.noao.edu:/usr/src/sys/compile/HUSA  i386
 > 
 > >Description:
 > Memory file system when mounted automatically from /etc/fstab does
 > not yield the size filesystem requested.  It appears that ~32MB is
 > what you get regardless of what you want, but I have not tried this
 > for sizes smaller than 32MB.  (Previously, the size was about the
 > size of the partition [I think].)  This began happening, I believe,
 > some time in August.
 > 
 > 
 > >How-To-Repeat:
 > If /etc/fstab contains
 > 
 >   /dev/sd0s1b		/tmp		mfs	rw,-s=131072	0	0
 > 
 > a 'df' yields
 > 
 >   Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 >   mfs:28          31404        4    28888     0%    /tmp
 > 
 > 
 > However, it DOES work to mount a filesystem manually with
 > 
 >    mount -t mfs -o -s=131072 /dev/sd1s1b /mnt
 > 
 > This yields 
 > 
 >    Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
 >    mfs:288         63567        1    58481     0%    /mnt
 > 
 > although this is not really an acceptable work-around for /tmp.
 > 
 > >Fix:
 > 
 > >Audit-Trail:
 > >Unformatted:
 > 
 
 /* 
    Matthew N. Dodd		| A memory retaining a love you had for life	
    winter@jurai.net		| As cruel as it seems nothing ever seems to
    http://www.jurai.net/~winter | go right - FLA M 3.1:53	
 */
 
State-Changed-From-To: open->analyzed 
State-Changed-By: phk 
State-Changed-When: Sun Apr 26 10:46:44 PDT 1998 
State-Changed-Why:  
should probably be fixed. 
State-Changed-From-To: analyzed->closed 
State-Changed-By: jmg 
State-Changed-When: Sun Apr 26 16:12:48 PDT 1998 
State-Changed-Why:  
this has been working for a LONG time...  as the follow up states, it's a user 
error... not a FreeBSD problem... 

I'm running a 450meg mfs /tmp on myu 2.2.1-R box...  I had to increase 
MAXDSIZ and DFLDSIZ but it does work perfectly fine... 
/etc/fstab: 
/dev/sd1b               /tmp                    mfs     rw,nosuid,-s=924288 0 0 
>Unformatted:
