Date: Mon, 06 Mar 2006 16:34:06 -0500 From: Chad Whitacre <chad@zetaweb.com> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions@freebsd.org Subject: possible umount bugs (was Re: "Panic: unmount: dangling vnode") Message-ID: <440CAACE.7000504@zetaweb.com> In-Reply-To: <20060306211051.GA50768@xor.obsecurity.org> References: <duhh6j$d00$1@sea.gmane.org> <20060306205736.GA50469@xor.obsecurity.org> <440CA2FD.3070804@zetaweb.com> <20060306211051.GA50768@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris, > A number of problems with umount are due to be fixed in 6.1 ... Wow, ok. Thanks for the heads-up. That's honestly a little disappointing to hear. I had hoped it was a problem with my backup script. I posted a fuller description of this and another problem last week. Here's the archive link: http://lists.freebsd.org/pipermail/freebsd-questions/2006-March/114825.html The two notes I would add to that post are: 1. The "dangling vnode" symptom did happen one other time when the box first came online several months ago. The other sysadmin rebooted and no further action was taken. 2. We do not have a core dump from the latest "dangling vnode" bout, due to the system apparently hanging. Is it likely that known umount problems explain the other symptom ("umount: unmount of /backup failed: Device busy")? 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 again for your help! chad Kris Kennaway wrote: > On Mon, Mar 06, 2006 at 04:00:45PM -0500, Chad Whitacre wrote: >> Kris, >> >> Thanks for the reply. >> >>> What version of FreeBSD? >> whit537@www2$ uname -a >> FreeBSD www2.svsd.net 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 >> 09:36:13 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC >> i386 >> whit537@www2$ > > A number of problems with umount are due to be fixed in 6.1, but are > not yet committed to the 6.x tree. Depending on how much of a problem > this is for you, you should test the candidate patch that Jeff > Roberson posted to stable@ a few days ago (check the archives). In > fact it would be very useful to know whether it fixes the issue; if it > does not we need to know ASAP if this is to be fixed in time for 6.1. > > Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440CAACE.7000504>