Date: Tue, 26 May 1998 14:09:06 -0400 From: Kenneth Miller <kemiller@hcs.harvard.edu> To: freebsd-stable@FreeBSD.ORG Subject: Re: improper shutdown Message-ID: <19980526140906.30830@hcs.harvard.edu> In-Reply-To: <19980525233116.10709@hcs.harvard.edu>; from Kenneth Miller on Mon, May 25, 1998 at 11:31:16PM -0400 References: <19980525233116.10709@hcs.harvard.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 05/25/98 at 11:31:16 PM, Kenneth Miller wrote: > > I've had a minor (?) but irritating problem ever since moving to stable > from 2.2.5. When I reboot, the disks don't have their clean flags set > and need fscking. If I shutdown to singer user mode and manually > unmount the disks, and remount / readonly, it's fine. But using the > shutdown program to go all the way doesn't work. I will assume this is > some misconfiguration on my part, but I was a little perplexed that it > began only when I moved to stable. > > Any suggestions or answers appreciated. OK. After a little more poking, it became apparent that what was happening was that certain filesystems were still busy, causing the reboot syscall to give up and halt without unmounting the filesystems. Why, then, would they be busy? All other processes should have been terminated, and no error message appeared indicating anything else. I also noticed that nothing is done with the RB_POWEROFF flag, even though APM support has been in there for a while. Any particular reason that anyone knows of? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980526140906.30830>