From owner-freebsd-current Mon Dec 6 11: 9:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (Postfix) with ESMTP id 3556E154EC for ; Mon, 6 Dec 1999 11:08:41 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from skylink.it (va-143.skylink.it [194.185.55.143]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id UAA18307; Mon, 6 Dec 1999 20:00:40 +0100 Received: from localhost (localhost [127.0.0.1]) by skylink.it (8.9.3/8.9.3) with ESMTP id RAA02816; Mon, 6 Dec 1999 17:36:20 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 6 Dec 1999 17:36:20 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@henny.jrc.it Reply-To: Nick Hibma To: Alex Zepeda Cc: Poul-Henning Kamp , vallo@matti.ee, "Brian W. Buchanan" , FreeBSD CURRENT Mailing List Subject: Re: mount(2) broken? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Please update your /dev entries. You need to copy MAKEDEV from the > > source area (it isn't installed by default) and run it with the right > > arguments to recreate the device nodes you need. > > I've seen this exact same thing before too. In fact it was two rather > annoying things, one being a single solitary last buffer that wouldn't > sync and thus left the whole fs marked dirty, and then fsck would check > it, see it was fine, but mount wouldn't recognize that it was clean. > > 'Course I saw this this morning too. Yes, with a new kernel, new devices, > ata driver, and new world. 'Twas very odd. Most probably this is exactly the problem I was describing to you a couple of days ago on IRC, phk. The solution is to boot single user, fsck / and reboot. After that things are back to normal. Even crashing the machine does not make this problem reoccur. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message