From owner-freebsd-hackers Fri Oct 1 12:39:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 97197152B5 for ; Fri, 1 Oct 1999 12:39:51 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id PAA08041 for ; Fri, 1 Oct 1999 15:39:51 -0400 (EDT) Date: Fri, 1 Oct 1999 15:25:25 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: block I/O on a locked vnode Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following is copied from the comments of FFS code: "Block devices associated with filesystems may have new I/O requests posted for them even if the vnode is *locked*, so no amount of trying will get them clean. Thus we give block devices a good effort, then just give up. For all other file types, go around and try again until it is clean." Can anyone explain to me when this situation will occur and, preferrably, point to the place of the related source code? Any help is appreciated. -------------------------------------------------- Zhihui Zhang. Please visit http://www.freebsd.org -------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message