From owner-freebsd-fs Tue Jan 4 8:19:23 2000 Delivered-To: freebsd-fs@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id E36BD14A19 for ; Tue, 4 Jan 2000 08:19:14 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id RAA25737; Tue, 4 Jan 2000 17:18:54 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA15519; Tue, 4 Jan 2000 17:18:52 +0100 (MET) Date: Tue, 4 Jan 2000 17:18:52 +0100 From: Eivind Eklund To: Mccrobie Charles Arn Cc: fs@FreeBSD.org Subject: Re: your mail Message-ID: <20000104171852.D13922@bitbox.follo.net> References: <200001031827.NAA11389@aplcenMP.apl.jhu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001031827.NAA11389@aplcenMP.apl.jhu.edu>; from mccrobi@aplcenMP.apl.jhu.edu on Mon, Jan 03, 2000 at 01:27:54PM -0500 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jan 03, 2000 at 01:27:54PM -0500, Mccrobie Charles Arn wrote: > Hello, > > I have some questions about file systems under FreeBSD. > > 1) I want to keep a vnode reference in the FS mount private data. > How does the file system avoid having "reclaim" called on this vnode? > Do I need to tract the "state" of the vnode and recreate it if its > reclaimed? No - just call vref() on the vnode. > 2) The above defers the LBN->physical mapping to the VOP_BMAP procedure. Is > this the "preferred" method or should I just perform that mapping through > use of a "private" procedure? I belive using VOP_BMAP is the preferred method. I'm sure somebody will correct me if I'm wrong. > 3) It seems the CD9660 file system doesn't do the following: > > a) Handle interleaved files. I found nothing in the BMAP that accounts > for file gap. Furthermore, only the header contains file_unit_size > and interleave. I assume no data CD's have been produced with > interleaved files. Just the same, it does seem to be an oversight... > > b) Handle multi-extent files. As I understand ISO 9660, there may be > more than one entry for a file which differs only in the "multi extent > flag" being set. This allows for multiple non-contiguous extents for > a single file. Again, I found no references to "multi extents" in the > code. Am I missing something here? I don't think there are any active CD9660 experts, so you are unlikely to get answers for this. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message