From owner-freebsd-questions Mon Mar 5 4:28: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-158.dsl.lsan03.pacbell.net [63.207.60.158]) by hub.freebsd.org (Postfix) with ESMTP id 435BE37B718 for ; Mon, 5 Mar 2001 04:28:06 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 62B8E66E7E; Mon, 5 Mar 2001 04:28:05 -0800 (PST) Date: Mon, 5 Mar 2001 04:28:04 -0800 From: Kris Kennaway To: Walter Hop Cc: FreeBSD Questions Subject: Re: tar just doesn't want to be KILLed Message-ID: <20010305042804.A80229@mollari.cthul.hu> References: <139127338372.20010305022456@binity.com> <20010304172518.B41178@mollari.cthul.hu> <58127691761.20010305023050@binity.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <58127691761.20010305023050@binity.com>; from walter@binity.com on Mon, Mar 05, 2001 at 02:30:50AM +0100 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 05, 2001 at 02:30:50AM +0100, Walter Hop wrote: > [in reply to kris@obsecurity.org, 05-03-2001] >=20 > >> 1. there's no way to get rid of an instance of tar (that's probably > >> waiting for some IO to complete? > >> 2. there's no way to umount a mount point held by such a process? > > > > No and no. See the KILL signal, and the -f option to umount. >=20 > Sorry, I should have provided more information, but thought it too > obvious. >=20 > slash:~# killall -KILL tar > slash:~# ps waux | grep tar > root 8975 0.0 0.1 548 0 p0- DE 4:03AM 2:14.08 tar cvfl /= mnt/dump/root.tar / > slash:~# umount -f /mnt/dump > umount: unmount of /mnt/dump failed: Device busy >=20 > [btw, /mnt/dump is a dead NFS mount and tar is in the 'sbwait' state] Okay, NFS is the exception here. You get this behaviour if the remote system dies and you're not mounting the NFS volume the correct way, but I'm not enough of an NFS expert to remember which options you should include to fix it. I always mount my NFS volumes as follows..I forget all the reasons why :-) rw,bg,soft,intr,nfsv3,rdirplus,mntudp,noconn Kris --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6o4ZUWry0BWjoQKURAq7iAKDt7twoTZt/Y+F4MByuUpS+EG1mxQCgjTTm BBxDlcWtbtCJu0gZViqD3Es= =LHMz -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message