Date: Wed, 27 Mar 2013 17:34:34 -0700 (PDT) From: Velcro Leaf <velcroleaf@rocketmail.com> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: filesystems don't properly dismount Message-ID: <1364430874.88614.YahooMailNeo@web164505.mail.gq1.yahoo.com> In-Reply-To: <alpine.GSO.1.10.1303271434190.9389@multics.mit.edu> References: <1364380546.45116.YahooMailNeo@web164504.mail.gq1.yahoo.com> <alpine.GSO.1.10.1303271239300.9389@multics.mit.edu> <1364403642.40164.YahooMailNeo@web164501.mail.gq1.yahoo.com> <alpine.GSO.1.10.1303271434190.9389@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
=A0Benjamin Kaduk wrote:=0A=0A> At this point, I think the most useful info= rmation would be the kernel messages =0A> from shutdown time, printed on th= e console.=A0 Do you have a serial console (makes =0A> this easy)? Otherwis= e, you may have to take a picture or video of the machine as =0A> it shuts = down.=0A=0AThe video was a great idea.=A0 I'm glad I didn't put forth the e= ffort to dust off an old terminal, because now the two servers are quietly = and happily rebooting.=A0 This is good news, but also annoying.=0A=0AIt's p= ossible that every time I saw the system reboot sloppily, it was still in t= he process of being updated (that is, only part of the way through the free= bsd-update procedure).=0A=0AOnce I noticed the issue, I stopped rebooting u= nnecessarily, so it could be that I stopped rebooting right at the point at= which things worked themselves out.=0A=0AI've got some kernel tweaking to = do, so if the issue comes back, I'll be ready with the video.=A0 No more re= booting remotely until I either catch it in the act or give up the hunt.=0A= =0AThanks for your response, it helped me get a little farther down the roa= d.=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1364430874.88614.YahooMailNeo>