> Russ' answer has me even more curious as to whether
> a copy of the whole file sits in the cache? I would
> tend to assume not from his answer,
> but I'm hoping to get a definitive answer on this.
> We have users who will be
> loading libraries up to one gig.
As a file is accessed, AFS pulls over sections
of the file as needed. These sections are
called "chunks" and are usually 64KB is size.
(You can set a different size on the afsd command
line.) The application (or kernel) reading the
file sees the correct, uninterrupted stream
of bytes while the AFS client code does the
work of getting chunks cached and throwing
away one of the least recently used chunks. A one
gigabyte library file will be read correctly by
the "ld" link-editor even with other AFS file
accesses occuring at the same time.
There's some information about this in the
Transarc "AFS System Administrators Guide".
There's also a decent, if I do say so myself,
explanation of the process in the book,
"Managing AFS: The Andrew File System",
Prentice-Hall, ISBN 0-23-802729-3.
===
Richard Campbell
[EMAIL PROTECTED]
VoiceMail,Fax:+1.212.214.0618
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
