Date: Mon, 06 Dec 1999 22:04:14 -0800 From: Mike Smith <msmith@freebsd.org> To: Alex Zepeda <jazepeda@pacbell.net> Cc: FreeBSD CURRENT Mailing List <current@freebsd.org> Subject: Re: mount(2) broken? Message-ID: <199912070604.WAA00482@mass.cdrom.com> In-Reply-To: Your message of "Mon, 06 Dec 1999 21:50:24 PST." <Pine.BSF.4.10.9912062149310.255-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, 6 Dec 1999, Nick Hibma wrote: > > > 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. > > Nah. This is about the third time I've seen this. I hadn't really > gathered any useful information (and no data was lost) so I didn't bother > to report it. I suspect it has something to do with soft-updates however. <aol> Me too. </aol> I just manifested this after a particularly nasty crash this evening (about 500 outstanding buffers), but softupdates weren't active. (It's too easy to kill the system with them enabled; there's a whole realm of exploration still untouched there.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com 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?199912070604.WAA00482>