From owner-freebsd-current@FreeBSD.ORG Thu Jul 24 11:58:48 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0197F37B404 for ; Thu, 24 Jul 2003 11:58:48 -0700 (PDT) Received: from milla.ask33.net (milla.ask33.net [217.197.166.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id E02D243FB1 for ; Thu, 24 Jul 2003 11:58:46 -0700 (PDT) (envelope-from nick@milla.ask33.net) Received: by milla.ask33.net (Postfix, from userid 1001) id 02E073ABB51; Thu, 24 Jul 2003 20:59:22 +0200 (CEST) Date: Thu, 24 Jul 2003 20:59:22 +0200 From: Pawel Jakub Dawidek To: Poul-Henning Kamp Message-ID: <20030724185922.GZ43543@garage.freebsd.pl> References: <20030724182836.GY43543@garage.freebsd.pl> <34180.1059071882@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VjP/dwTbBl6I9PQk" Content-Disposition: inline In-Reply-To: <34180.1059071882@critter.freebsd.dk> X-PGP-Key-URL: http://garage.freebsd.pl/jules.asc X-OS: FreeBSD 4.8-RELEASE i386 X-URL: http://garage.freebsd.pl User-Agent: Mutt/1.5.1i cc: freebsd-current@freebsd.org Subject: Re: File system deadlock. GBDE(4) and/or MD(4) related. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 18:58:48 -0000 --VjP/dwTbBl6I9PQk Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 24, 2003 at 08:38:02PM +0200, Poul-Henning Kamp wrote: +> >+> What you have found has nothing to do with GBDE, I think it is the +> >+> usual "vnode backed md(4)" deadlock. +> > +> >Hmm? So you're trying to tell that this is somehow normal behaviour? +>=20 +> We've had problems like this before with vnode backed MD(4) devices +> (and vn(4) devices before that). +>=20 +> One way or another: It is _not_ a GBDE problem. Hey, Poul! I'm not trying to show that gbde(4) is a buggy software, I'm not trying to destroy you work, your image or FreeBSD, really. I believe that this isn't bug in gbde(4), my fault, sorry. But one thing I know, is that bug is somewhere and I just want to help track it down. This information could be useful: When I've mounted file system on /private (not on /mnt/private) there is no problem anymore. So maybe deadlock is caused by some directory locking or something? Because if file system in mounted on /mnt/private deadlock is 100% reproducable. --=20 Pawel Jakub Dawidek pawel@dawidek.net UNIX Systems Programmer/Administrator http://garage.freebsd.pl Am I Evil? Yes, I Am! http://cerber.sourceforge.net --VjP/dwTbBl6I9PQk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iQCVAwUBPyAsij/PhmMH/Mf1AQGzgAP/TGdH1UXXqJhZhIB4bBQPH/9mHK3ab6Fb WgaoMsACeCxal8nv9dROP2YNDCjSDvewWc6HYSw+RSioZpXRY4kelpLJIrb+7L/u aFUCv9jTjHmW3YI1+NYYEa0pMMU5QnNF5NiB8+2lKc2QHFk+frMcgGBqCcgyZ7F7 GODA37v52Cc= =Vhwr -----END PGP SIGNATURE----- --VjP/dwTbBl6I9PQk--