Date: 7 Apr 96 09:40:48 GMT From: peter@jhome.DIALix.COM (Peter Wemm) To: freebsd-current@freebsd.org Subject: Re: Clean reboot on current Message-ID: <peter.828870048@jhome.DIALix.COM> References: <199604051606.LAA21264@hopf.math.purdue.edu>, <199604061004.TAA03574@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
msmith@atrad.adelaide.edu.au (Michael Smith) writes: >Clarence Wilkerson stands accused of saying: >> When I do a few syncs and a "reboot" command, I get a string of >> numbers like >> >> 3 3 3 3 3 3 "giving up" >The '3' indicates the number of disk buffers that are waiting to be >written. Do you get the same result with 'shutdown -r now'? >If not, then you probably have an application that's unhappy about being >nuked. If somebody gets this and has the tech ability to decode the fs layout and find what blocks these correspond do and track down the bugs in the kernel that cause this, you might try: "options SHOW_BUSYBUFS" in your kernel config file. What I find annoying is when there's one block left, and it's on a MFS'ed /tmp and the clean shutdown is aborted because of the unclean ramdisk. :-( (hint: MFS devices use a major number of 0xff, so the remaining blocks appear on dev 0x0000ffxx and so on) -Peter >> Clarence Wilkerson >-- >]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ >]] Genesis Software genesis@atrad.adelaide.edu.au [[ >]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ >]] realtime instrument control (ph/fax) +61-8-267-3039 [[ >]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?peter.828870048>