From owner-freebsd-stable  Fri Sep 12 20:07:40 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA29004
          for stable-outgoing; Fri, 12 Sep 1997 20:07:40 -0700 (PDT)
Received: from set.spradley.dyn.ml.org (fcn104-32.tmi.net [207.170.104.32])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA28996
          for <freebsd-stable@FreeBSD.ORG>; Fri, 12 Sep 1997 20:07:36 -0700 (PDT)
Received: from set.spradley.dyn.ml.org (tsprad@localhost [127.0.0.1])
	by set.spradley.dyn.ml.org (8.8.5/8.8.5) with ESMTP id WAA14604;
	Fri, 12 Sep 1997 22:18:33 -0500 (CDT)
Message-Id: <199709130318.WAA14604@set.spradley.dyn.ml.org>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Edward Ajhar <ajhar@noao.edu>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: mfs does not mount properly 
In-reply-to: Your message of "Fri, 12 Sep 1997 15:47:46 PDT."
             <199709122247.PAA00293@husa.tuc.noao.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 12 Sep 1997 22:18:31 -0500
From: Ted Spradley <tsprad@metronet.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Just another data point:  I have a system running the May 22, 1997 
3.0-Snapshot, and it has this behavior.  I have a 512 Mbyte swap partition that
I use for a memory file system, with this in my fstab:

# Device                Mountpoint      FStype  Options         Dump    Pass#
/dev/wd0s1b             /tmp            mfs     rw              0       0

It shows in df(1) like this:

Filesystem     1K-blocks     Used    Avail Capacity  Mounted on
mfs:22             31039        8    28548     0%    /tmp

swapinfo(8) says:

Device      1K-blocks     Used    Avail Capacity  Type
/dev/wd0s1b    512000    54728   457208    11%    Interleaved

I never tried mounting it from a command.

> ...  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].)  Is this a bug, or have I missed something?