From owner-freebsd-hackers Mon Apr 26 11:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id AF4B314C03 for ; Mon, 26 Apr 1999 11:26:52 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA47015; Mon, 26 Apr 1999 11:26:48 -0700 (PDT) (envelope-from dillon) Date: Mon, 26 Apr 1999 11:26:48 -0700 (PDT) From: Matthew Dillon Message-Id: <199904261826.LAA47015@apollo.backplane.com> To: Luoqi Chen Cc: freebsd-hackers@FreeBSD.ORG, zzhang@cs.binghamton.edu Subject: Re: Logical block number caching References: <199904261612.MAA15096@lor.watermarkgroup.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> the block device for a partition to be opened while that partition is :> mounted and vice versa. :> :> Is this the same situation with FreeBSD 3.1? I have tried to find where in :> the source code this gets handled without luck. I hope someone will tell :> me whether FreeBSD uses the same strategy and which routines handle this. :> :> Any help is appreciated. :> :> -------------------------------------------------- :> Zhihui Zhang. Please visit http://www.freebsd.org :> -------------------------------------------------- :> :I believe it still applies to FreeBSD. The code that prevents mounted block :device from being opened is in miscfs/specfs/spec_vnops.c : :-lq Yes, and it would be extremely dangerous to allow any block device that the filesystem also has a handle on to be separately openned. There is no real cache coherency between logical and physical blocks - the filesystem code manages it all very carefully. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message