Date: Mon, 6 Mar 2006 16:44:19 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Chad Whitacre <chad@zetaweb.com> Cc: freebsd-questions@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: possible umount bugs (was Re: "Panic: unmount: dangling vnode") Message-ID: <20060306214419.GA51866@xor.obsecurity.org> In-Reply-To: <440CAACE.7000504@zetaweb.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
--cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 06, 2006 at 04:34:06PM -0500, Chad Whitacre wrote: > Kris, >=20 > > A number of problems with umount are due to be fixed in 6.1 ... >=20 > Wow, ok. Thanks for the heads-up. That's honestly a little disappointing= =20 > to hear. I had hoped it was a problem with my backup script. The rule of thumb is that user code should not cause kernel panics. But all software has bugs, of course. > I posted a fuller description of this and another problem last week.=20 > Here's the archive link: >=20 > http://lists.freebsd.org/pipermail/freebsd-questions/2006-March/114825.ht= ml >=20 >=20 > The two notes I would add to that post are: >=20 > 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. >=20 > 2. We do not have a core dump from the latest "dangling vnode" bout, > due to the system apparently hanging. >=20 >=20 > Is it likely that known umount problems explain the other symptom=20 > ("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. > This is actually a production box, so I can't do too much testing on it.= =20 > I may be able to install the patch, though, in which case I will report= =20 > back. Thanks. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEDK0zWry0BWjoQKURAmo1AKCODob4yKBCZ0LENb6Qdc4dm0T+LACfVxHr Qy4SFvn9vAEZBRc257iQGgc= =8QfD -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060306214419.GA51866>