From owner-freebsd-current Thu Aug 2 2:59:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 7974237B401 for ; Thu, 2 Aug 2001 02:59:34 -0700 (PDT) (envelope-from sheldonh@starjuice.net) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.31 #1) id 15SFAZ-000EtB-00; Thu, 02 Aug 2001 11:53:31 +0200 From: Sheldon Hearn To: Brian Somers Cc: kc5vdj@yahoo.com, freebsd-current@FreeBSD.ORG, brian@freebsd-services.com Subject: Re: /home: mount pending error: blocks 14 files 3 In-reply-to: Your message of "Thu, 02 Aug 2001 10:42:29 +0100." <200108020942.f729gT859796@hak.lan.Awfulhak.org> Date: Thu, 02 Aug 2001 11:53:31 +0200 Message-ID: <57236.996746011@axl.seasidesoftware.co.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 02 Aug 2001 10:42:29 +0100, Brian Somers wrote: > If the error keeps turning up, I would guess that you have a 0 or > empty fsck field in /etc/fstab and fsck -s therefore not fixing the > problem. Nope. I have passno set for the filesystem on which I also see this. I used to have background fsck enabled, but I disabled it because of horrid unkillable fsck behaviour. Perhaps background fsck did something nasty to my filesystem that normal fsck isn't seeing? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message