From owner-freebsd-questions@FreeBSD.ORG Wed Feb 2 04:02:55 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69A6416A4CE; Wed, 2 Feb 2005 04:02:55 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14BF543D41; Wed, 2 Feb 2005 04:02:55 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 0A5451299B9; Wed, 2 Feb 2005 00:02:54 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 48141-09; Wed, 2 Feb 2005 04:02:53 +0000 (GMT) Received: from ganymede.hub.org (blk-224-186-245.eastlink.ca [24.224.186.245]) by hub.org (Postfix) with ESMTP id 7D954129304; Wed, 2 Feb 2005 00:02:53 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 00D8E39CEC; Wed, 2 Feb 2005 00:02:51 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id F0EEC39AE3; Wed, 2 Feb 2005 00:02:51 -0400 (AST) Date: Wed, 2 Feb 2005 00:02:51 -0400 (AST) From: "Marc G. Fournier" To: Greg 'groggy' Lehey In-Reply-To: <20050202000752.GJ49172@wantadilla.lemis.com> Message-ID: <20050201235936.O89998@ganymede.hub.org> References: <20050131195340.K89998@ganymede.hub.org> <20050202000752.GJ49172@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 4.x, vinum and vrlock ... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Feb 2005 04:02:55 -0000 On Wed, 2 Feb 2005, Greg 'groggy' Lehey wrote: > On Monday, 31 January 2005 at 20:02:50 -0400, Marc G. Fournier wrote: >> >> What exactly does this mean? >> >> /proc/43414/status:rsync 43414 42774 23799 14838 5,1 ctty 1107214940,71735 >> 3,779921 33,791868 vrlock 0 0 0,0,0,2,3,4,5,20,31 - >> /proc/43479/status:postgres 43479 144 144 144 -1,-1 noflags >> 1107214989,263828 0,0 1,63591 vrlock 70 70 70,70,70 - >> /proc/7/status:bufdaemon 7 0 0 0 -1,-1 noflags 1107140099,155 0,0 61,876619 >> vrlock 0 0 0,0 - >> /proc/9/status:syncer 9 0 0 0 -1,-1 noflags 1107140099,192 0,0 259,373334 >> vrlock 0 0 0,0 - > > It looks like breakage from your MUA. I've deleted the rest; it's > too painful. > >> I seem to get it a fair amount when I'm starting up a jail, where >> the 'umount' in the start scripts just hangs there seemingly >> indefinitely ... > > If you're talking about the vrlock state, it's used for locking bands > when updating striped plexes. If it hangs around for any length of > time, it'll be a deadlock. Have you been killing processes? Has > anybody else seen this? I have not been killing processes ... seems to happen more often when I'm using rsync to copy a directory hierarchy from one server to the other though ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664