From owner-freebsd-bugs  Sat Nov 22 20:52:36 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA18178
          for bugs-outgoing; Sat, 22 Nov 1997 20:52:36 -0800 (PST)
          (envelope-from owner-freebsd-bugs)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18172;
          Sat, 22 Nov 1997 20:52:29 -0800 (PST)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id PAA15123; Sun, 23 Nov 1997 15:51:01 +1100
Date: Sun, 23 Nov 1997 15:51:01 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199711230451.PAA15123@godzilla.zeta.org.au>
To: cagney@tpgi.com.au, freebsd-bugs@freebsd.org, jmg@freebsd.org
Subject: Re: conf/5127
Sender: owner-freebsd-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>Synopsis: Can't mount mfs file system larger than 38mb from fstab
>
>State-Changed-From-To: open-closed
>State-Changed-By: jmg
>State-Changed-When: Sat Nov 22 14:46:52 PST 1997
>State-Changed-Why: 
>modifing daemon resource limits in /etc/login.conf is a better way to
>handle this...

And has already been handled after 2.2.5 was released.  See revisions
1.14 and 1.9.2.4 of src/etc/login.conf.

The problems are that mount_mfs is too conservative to raise its
soft data limit above its hard data limit, and the hard data limit
in /etc/login.conf was too conservative.

See also revisions 1.17 and 1.20 of src/usr.sbin/newfs/mkfs.c.

Bruce