Date: Tue, 7 Dec 1999 08:16:47 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Mike Smith <msmith@FreeBSD.ORG> Cc: Alex Zepeda <jazepeda@pacbell.net>, FreeBSD CURRENT Mailing List <current@FreeBSD.ORG> Subject: Re: mount(2) broken? Message-ID: <Pine.BSF.4.10.9912070815590.35050-100000@beppo.feral.com> In-Reply-To: <199912070604.WAA00482@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Happens to me every boot. And I'm up to date with all binaries and kernel. I don't have softupdates on the root filesystem. On Mon, 6 Dec 1999, Mike Smith wrote: > > 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 > 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.10.9912070815590.35050-100000>