From owner-freebsd-current Thu Aug 2 9:34: 0 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id CC38837B401 for ; Thu, 2 Aug 2001 09:33:56 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.217]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA25294; Thu, 2 Aug 2001 09:33:41 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <57236.996746011@axl.seasidesoftware.co.za> Date: Thu, 02 Aug 2001 09:33:41 -0700 (PDT) From: John Baldwin To: Sheldon Hearn Subject: Re: /home: mount pending error: blocks 14 files 3 Cc: brian@freebsd-services.com, freebsd-current@FreeBSD.org, kc5vdj@yahoo.com, Brian Somers 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 02-Aug-01 Sheldon Hearn wrote: > > > 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? I get these messages when I reboot or crash before the background fsck finishes sometimes. Sometimes I get them when the filesystems are clean, too. They always happen when the previous boot did a background fsck, however. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message