From owner-freebsd-current Fri Oct 13 8:18:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from roaming.cacheboy.net (roaming.cacheboy.net [203.56.168.69]) by hub.freebsd.org (Postfix) with ESMTP id E072437B502 for ; Fri, 13 Oct 2000 08:18:39 -0700 (PDT) Received: (from adrian@localhost) by roaming.cacheboy.net (8.11.0/8.11.0) id e9DFHbQ20523 for freebsd-current@freebsd.org; Fri, 13 Oct 2000 17:17:37 +0200 (CEST) (envelope-from adrian) Date: Fri, 13 Oct 2000 17:17:37 +0200 From: Adrian Chadd To: freebsd-current@freebsd.org Subject: HEADS UP: fsck wrappers gotcha Message-ID: <20001013171737.A20476@roaming.cacheboy.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As pointed out by mr Sobolev, the fsck wrappers will blindly try to execute fsck_$FS regardless of whether its there or not, and fail if it isn't. This is a gotcha for non-fsck'able fses right now, such as nfs and ntfs. The solution, which I forgot to add in my email, is to set pass to 0. This forces fsck to NOT consider the FS for fsck-on-boot, and should make things quieter. Note that swap / procfs in /etc/fstab already use dump/pass = 0, but this is just to make sure. Just FYI, Adrian -- Adrian Chadd "The main reason Santa is so jolly is because he knows where all the bad girls live." -- Random IRC quote To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message