From owner-freebsd-fs Tue Aug 22 9:54:33 2000 Delivered-To: freebsd-fs@freebsd.org Received: from hotmail.com (f72.pav1.hotmail.com [64.4.31.72]) by hub.freebsd.org (Postfix) with ESMTP id 7A69A37B423 for ; Tue, 22 Aug 2000 09:54:31 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 22 Aug 2000 09:54:31 -0700 Received: from 216.122.0.208 by pv1fd.pav1.hotmail.msn.com with HTTP; Tue, 22 Aug 2000 GMT X-Originating-IP: [216.122.0.208] From: "Chris Jones" To: freebsd-fs@freebsd.org Subject: Inode/DQuot locking problem with vnode disk Date: Tue, 22 Aug 2000 09:54:30 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 22 Aug 2000 16:54:31.0172 (UTC) FILETIME=[A4227C40:01C00C59] Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am currently trying to get quotas to work inside of a vnode disk (filesystem in a file (using UFS)). The problem is that I want the quotas to work inside of a jail which is running with the vnode disk as it's "root" directory. The problem that I'm having is that after turning on the quotas (this must be done outside of the jail), if I try to access a file which already has a quota, or I try to modify the quota using edquota (from inside of the jail), the process locks. Once the process is locked, there is no way to kill it, and any subsequent accesses to the vnode disk also locks. These processes will stop in 1 of 5 different tsleep statements (inode, chkdq1, chkdq2, chkiq1, or chkiq2). I am assuming that the problems is that the main filesystem puts a lock on the vnode disk file, and subsequently tries to lock the indoe inside of the file and is unable b/c of the previous lock on the vnode disk file. Has anyone else seen this? Any pointers would be greatly appreciated. Oh, yeah, the version is 4.0-STABLE. Thank you, Christophe ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message