Date: Sat, 12 Mar 2011 12:11:45 -0800 From: "Jason C. Wells" <jcw@speakeasy.net> To: Chris Brennan <xaero@xaerolimit.net> Cc: John Levine <johnl@iecc.com>, freebsd-questions@freebsd.org, Robert <traveling08@cox.net> Subject: Re: Unable to umount Message-ID: <4D7BD381.4020404@speakeasy.net> In-Reply-To: <AANLkTi=vDdnqogyFq65_QYtchrOis8WsF9CZZ3uorQ1z@mail.gmail.com> References: <20110312090634.3c1ce3ed@dell64> <20110312172959.65728.qmail@joyce.lan> <20110312093423.2b8f9eba@dell64> <AANLkTi=vDdnqogyFq65_QYtchrOis8WsF9CZZ3uorQ1z@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/12/11 09:51, Chris Brennan wrote: > 'umount -f' is dangerous, while it worked in your case, truly, make > sure you > don't have any open files in the future, just to ensure no loss of files or > filesytem corruption Run sync before umount -f to flush write caches. Later, Jason
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D7BD381.4020404>