Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!sun-barr!newstop!sun!amdahl!JUTS!ked01 From: ked01@ccc.amdahl.com (Kim DeVaughn) Newsgroups: comp.sys.amiga.tech Subject: Re: when is a block not a block? Message-ID: Date: 10 Aug 90 08:44:08 GMT References: <6498.269a4527@vax1.tcd.ie> <648H02l0b8KM01@amdahl.uts.amdahl.com> <13237@cbmvax.commodore.com> <3fco02lsb9LE01@amdahl.uts.amdahl.com> <13342@cbmvax.commodore.com> <10797@wehi.dn.mu.oz> peter@sugar.hackercorp.com (Peter da Silva) writes: > In article ked01@JUTS.ccc.amdahl.com (Kim DeVaughn) writes: > > While I understand that other such "oddities" may well arise in the future, > > what bothers me is not being able to ask the filesystem for the *true* info > > in a supported way. > > *which* filesystem? Whichever filesystem is being addressed at the time. There *is* a field in the FIB called fib_NumBlocks. What I would like is for that field to accurately reflect the actual number of blocks allocated (or some algorithmic variation thereof) by a file, at the time it is interrogated. That, and that a filesystem *document* what that field "means" in its own context. /kim -- UUCP: kim@uts.amdahl.com -OR- ked01@juts.ccc.amdahl.com or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25