Date: Mon, 6 Dec 1999 17:36:20 +0100 (CET) From: Nick Hibma <n_hibma@webweaving.org> To: Alex Zepeda <jazepeda@pacbell.net> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, vallo@matti.ee, "Brian W. Buchanan" <brian@CSUA.Berkeley.EDU>, FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: mount(2) broken? Message-ID: <Pine.BSF.4.20.9912061735160.2742-100000@henny.jrc.it> In-Reply-To: <Pine.BSF.4.10.9912051902020.257-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.20.9912061735160.2742-100000>