From owner-freebsd-current Sun Dec 5 19:13:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id EF48914E08 for ; Sun, 5 Dec 1999 19:13:21 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.116.115]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMA00CAKTV27U@mta2.snfc21.pbi.net> for current@FreeBSD.ORG; Sun, 5 Dec 1999 19:04:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 6E3889155D; Sun, 05 Dec 1999 19:04:14 -0800 (PST) Date: Sun, 05 Dec 1999 19:04:14 -0800 (PST) From: Alex Zepeda Subject: Re: mount(2) broken? In-reply-to: <16756.944388749@critter.freebsd.dk> To: Poul-Henning Kamp Cc: vallo@matti.ee, "Brian W. Buchanan" , current@FreeBSD.ORG 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 On Sun, 5 Dec 1999, Poul-Henning Kamp wrote: > >Same here, except I'm able to mount after fscking an rebooting. ATA disk > >and new ata drivers. > > 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. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message