From owner-freebsd-questions@FreeBSD.ORG Sun Apr 24 14:04:29 2005 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 5058716A4CE for ; Sun, 24 Apr 2005 14:04:29 +0000 (GMT) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71A7843D5E for ; Sun, 24 Apr 2005 14:04:28 +0000 (GMT) (envelope-from ertr1013@student.uu.se) Received: from falcon.midgard.homeip.net (212.181.162.201) by pne-smtpout1-sn1.fre.skanova.net (7.1.026.7) id 42650A3B00136D68 for freebsd-questions@freebsd.org; Sun, 24 Apr 2005 16:04:27 +0200 Received: (qmail 63575 invoked by uid 1001); 24 Apr 2005 14:04:26 -0000 Date: Sun, 24 Apr 2005 16:04:26 +0200 From: Erik Trulsson To: =?iso-8859-1?Q?K=F6vesd=E1n_G=E1bor?= Message-ID: <20050424140426.GA63497@falcon.midgard.homeip.net> Mail-Followup-To: =?iso-8859-1?Q?K=F6vesd=E1n_G=E1bor?= , freebsd-questions@freebsd.org References: <426BA3E7.4080707@t-hosting.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <426BA3E7.4080707@t-hosting.hu> User-Agent: Mutt/1.5.9i cc: freebsd-questions@freebsd.org Subject: Re: fsck in securelevel 2? 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: Sun, 24 Apr 2005 14:04:29 -0000 On Sun, Apr 24, 2005 at 03:49:27PM +0200, K=F6vesd=E1n G=E1bor wrote: > Hi, >=20 > I tried to check the root partition with fsck and it found errors and=20 > for my greatest surprise, it answered its questions automatically with=20 > no. It is due to the securelevel 2? I've been thinking whether fsck uses= =20 > direct access (which is denied by the securelevel) or not? Of course fsck uses some kind of direct access to the disk. It would not be able to identify and repair problems with the filesystem, if it had to go through the filesystem to access the disk. And to quote the manpage for init(8) (which describes what the various securelevels mean): "Setting the security level above 1 too early in the boot sequence can prevent fsck(8) from repairing inconsistent file systems." In the normal boot sequence fsck is run long before the securelevel is raised so this is normally not a problem. I hope the root partition had not been mounted as read/write when you ran fsck, because if you run fsck on partition which is mounted r/w fsck will often (incorrectly) report errors even if there are no problems, and then one can really mess things up. --=20 Erik Trulsson ertr1013@student.uu.se