[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  4-JAN-1991 09:39:07.92  To:	MRGATE::"ARISIA::EVERHART" CC:	4 Subj:	RE: File system help needed; FIDs inconsistent  * Received:  by crdgw1.ge.com (5.57/GE 1.80)( 	 id AA29309; Fri, 4 Jan 91 09:13:02 ESTX Received: From VENUS.YCC.YALE.EDU by CRVAX.SRI.COM with TCP; Fri,  4 JAN 91 05:47:53 PSTM Received: from BULLDOG.CS.YALE.EDU by Venus.YCC.Yale.Edu; Fri, 4 Jan 91 09:38   ESTO Received: from lrw.UUCP by BULLDOG.CS.YALE.EDU via UUCP; Fri, 4 Jan 91 08:36:25   ESTG Received: by lrw.UUCP (DECUS UUCP w/Smail); Fri,  4 Jan 91 08:10:04 EDT ! Date: Fri,  4 Jan 91 08:10:04 EDT ' From: Jerry Leichter <leichter@LRW.COM> 7 Subject: RE: File system help needed; FIDs inconsistent  To: INFO-VAX@KL.SRI.COM 4 Message-Id: <9101041336.AA09244@BULLDOG.CS.YALE.EDU>" X-Envelope-To: info-vax@kl.sri.COM  F 	If you do a directory of a file on the volume set, you get what you'dG 	expect for the file id (SEQ,VER,RVN), where RVN is the relative volume B 	number of the disk where the file actually resides.  With a bound0 	volume set of 2 disks, you always get a 1 or 2.  G 	Now, if you do a DUMP/HEADER on the file, it shows (SEQ,VER,0) instead > 	of the correct RVN!  The same occurs with DUMP/FILE_HEADER on 	INDEXF.SYS.  What's going on?  D 	Swing reads directory files and is getting zeroes as well, which isB 	what I suspect the problem is.  Since zero is the correct RVN forE 	disks which are not part of a bound volume set, it causes no trouble  	there.   A 	Can anyone explain why the FID is incorrect in INDEXF.SYS, but a G 	directory command returns the correct FID?  Any file system guru's out  	there?   K Well... here's a guess.  A FID consists of three fields:  File number, file N sequence number, and relative volume number (RVN).  Originally, each field wasM one word (16 bits) long.  However, disks have now gotten large enough that it K was reasonable to have more than 65K files on one of them; so a 16-bit file N number started to become something of a limitation.  To solve it, one byte wasN "stolen" from the RVN field.  This gives a 24-bit file number field, and up toL some 16 million files per disk, while still allowing 255 members in a volume set, which should be plenty.  M There's no direct way of telling, by looking at a FID, which format it is in. G I'm not sure how you make the distinction.  One guess is that you check J the maximum number of files allowed on the volume - $GETDVI characteristicJ MAXBLOCK - though there may be a bit in the volume header somewhere that IJ haven't noticed.  On the other hand, the documentation indirectly suggests4 that all newly-initialized disks use the new format.  J Few programs need to know:  A FID should generally be treated as an opaque0 data object, understood only by the file system.  J Any program that tries to format FID's needs to understand the new format.I Of the standard VMS utilities, I can think of a few off-hand that need to M format FID's:  DIRECTORY, DUMP, and ANALYZE/SYSTEM or /CRASH (for SHOW CHAN). M There may be a few more.  Obviously, some programs understand the new format,  while others do not!  L The "stolen" byte was the less-significant one of the RVN.  An RVN of 1 or 2L in the "old" format would have 1 or 2 in the less-significant byte, 0 in theL more-significant byte.  Look at the same data as being in the new format andI the more-significant byte becomes the entire RVN, and appears to be zero; K while the file number becomes (65536 or 131072) larger.  So it appears that M your disks have old-format FID's; DIRECTORY properly formats them (or perhaps K just plain doesn't understand new-format FID's); and  DUMP/HEADER and SWING E think that (at least some, probably all) FID's are in the new format.    							-- Jerry   