Subject: Re: Patch to disallow mounts of unclean FFS unless forced
To: Robert Elz <kre@munnari.OZ.AU>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 10/15/2003 09:31:03
--4SFOXa2GPu3tIq4H
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Oct 15, 2003 at 04:06:48AM +0700, Robert Elz wrote:
>     Date:        Tue, 14 Oct 2003 13:54:30 -0700
>     From:        Jason Thorpe <thorpej@wasabisystems.com>
>     Message-ID:  <9B679C26-FE88-11D7-B507-000A957650EC@wasabisystems.com>
>=20
>   | Use the -f flag to force the mount.
>=20
> But that is root only - users are supposed (with the right sysctl setting)
> to be able to mount too.

The thing is that our code at present assumes fsck has fixed the file=20
system, and it blindly moves forward. And so it panics if it gets to bad=20
places. If '-f' isn't root-only, then a user can make an unclean file=20
system, mount it, and panic the box.

If a user wants to mount a dirty file system, I think having to contact=20
the administrator is a fine thing to do.

Take care,

Bill

--4SFOXa2GPu3tIq4H
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQE/jXZHWz+3JHUci9cRAhosAJwMu+7/qxiaMh+OpUGT/HB1zBxkjwCfc6Ri
8b8y8Nx+fq/ae64u2QCEdqA=
=zB+7
-----END PGP SIGNATURE-----

--4SFOXa2GPu3tIq4H--