Date: Mon, 06 Mar 2006 16:52:24 -0500 From: Chad Whitacre <chad@zetaweb.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: Re: possible umount bugs (was Re: "Panic: unmount: dangling vnode") Message-ID: <440CAF18.4080605@zetaweb.com> In-Reply-To: <20060306214419.GA51866@xor.obsecurity.org> References: <duhh6j$d00$1@sea.gmane.org> <20060306205736.GA50469@xor.obsecurity.org> <440CA2FD.3070804@zetaweb.com> <20060306211051.GA50768@xor.obsecurity.org> <440CAACE.7000504@zetaweb.com> <20060306214419.GA51866@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris,
> The rule of thumb is that user code should not cause kernel panics.
Good to know, thanks.
> But all software has bugs, of course.
Understood. This is just the first bug I've personally hit in FreeBSD in
4 years of use. /me weeps for his lost innocence
>> Is it likely that known umount problems explain the other symptom
>> ("umount: unmount of /backup failed: Device busy")?
>
> That's completely standard and just means something still had a file
> open on that filesystem. Use fstat or lsof to find out what.
Another good tip, thanks.
>> This is actually a production box, so I can't do too much testing on it.
>> I may be able to install the patch, though, in which case I will report
>> back.
>
> Thanks.
Let me know if there's any other info besides a patch report that might
be helpful.
chad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440CAF18.4080605>