From owner-freebsd-current@FreeBSD.ORG Thu Jul 24 13:01:12 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 5F58A37B401 for ; Thu, 24 Jul 2003 13:01:12 -0700 (PDT) Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44E4B43F85 for ; Thu, 24 Jul 2003 13:01:11 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by phk.freebsd.dk (8.12.8/8.12.8) with ESMTP id h6OK19V3069454; Thu, 24 Jul 2003 20:01:09 GMT (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h6OK185H034782; Thu, 24 Jul 2003 22:01:09 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Pawel Jakub Dawidek From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 24 Jul 2003 20:59:22 +0200." <20030724185922.GZ43543@garage.freebsd.pl> Date: Thu, 24 Jul 2003 22:01:08 +0200 Message-ID: <34781.1059076868@critter.freebsd.dk> 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 20:01:12 -0000 In message <20030724185922.GZ43543@garage.freebsd.pl>, Pawel Jakub Dawidek writ es: >+> 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. No worries, I just want to make sure that the mail archives contain a definitive statement that this was not a GBDE problem. >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. Using vnode backed md(4) devices is sort of incestuous, and that may be what happens here: For certain operations it is necessary to lock all the way to the top of the filesystem, and this may be what results in a deadlock for you now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.