From owner-freebsd-questions@FreeBSD.ORG Sun Apr 25 17:28:57 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1800016A4CE for ; Sun, 25 Apr 2004 17:28:57 -0700 (PDT) Received: from mtaw6.prodigy.net (mtaw6.prodigy.net [64.164.98.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB7D143D2D for ; Sun, 25 Apr 2004 17:28:56 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (7a687ef8927ac3969298e5a2bcc3ed4e@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128]) by mtaw6.prodigy.net (8.12.10/8.12.10) with ESMTP id i3Q0RgpT028147; Sun, 25 Apr 2004 17:27:42 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 991D452322; Sun, 25 Apr 2004 17:28:55 -0700 (PDT) Date: Sun, 25 Apr 2004 17:28:55 -0700 From: Kris Kennaway To: andy_park@nospammail.net Message-ID: <20040426002855.GA49376@xor.obsecurity.org> References: <3C73D6BD-9718-11D8-931D-000393A4799C@nospammail.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <3C73D6BD-9718-11D8-931D-000393A4799C@nospammail.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@FreeBSD.ORG Subject: Re: Auto-mounting ext2 slices X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Apr 2004 00:28:57 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 26, 2004 at 01:25:35AM +0100, andy_park@nospammail.net wrote: > Hi, I have recently installed FreeBSD 4.9 on my fileserver to replace=20 > RH9, and have put my ext2 slice in /etc/fstab so they mount on bootup.=20 > The entry on /etc/fstab is as follows: >=20 > /dev/ad1s5 /mnt/data2 ext2fs rw 0 = =20 > 2 >=20 > However I recently experienced a blackout, and on the next boot, ext2=20 > slice, marked 'dirty', wasn't fsck'ed automatically, preventing the=20 > normal boot process from finishing. Is this normal behaviour? If so,=20 > how would one set up an ext2 slice to auto-mount on bootup, and fsck=20 > itself if marked dirty so it continues to mount as rw? You need to have fsck_ext2fs installed. This is included in the e2fsprogs port. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAjFfHWry0BWjoQKURAknCAKC7pyCRy26IP6OZNRkcRwZm7jYfUACgx51u oYWrWjJBwuunxLq9G7XdIpc= =GdaT -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S--