For those not familiar with mkisofs, it is a tar-like utility used to create CDROM images from a tree of files. While creating an image with mkisofs, the following kind of thing happens: AFS using 120689 of the cache's available 108134 1K byte blocks. [Cache guideline temporarily deliberately exceeded; it will be adjusted down but you may wish to increase the cache size.] Eventually mkisofs gets a read error on a perfectly good file. We have produced a fair amount of scrap plastic this way. Our cache partition is like so: df /cache Filesystem Total KB free %used iused %iused Mounted on /dev/lv00 204800 52884 74% 16402 32% /cache cat /usr/vice/etc/cacheinfo /afs:/cache:163840 Do we _really_ have to allow more than the 25% cachesize slop we are allowing now? How does the cache manager get off writing checks for more disk than is in its account? Is this government software? This didn't happen with previous versions of AFS, but we may not have tried a large enough image. BTW, this is AIX 3.2.5. -Rick -- |Rick Cochran phone: 607-255-7223| |Cornell Materials Science Center FAX: 607-255-3957| |E20 Clark Hall, Ithaca, N.Y. 14853 email: [EMAIL PROTECTED]| | "The Founding Fathers did not establish the United States as a | | democratic republic so that elected officials would decide trivia, | | while all great questions would be decided by the judiciary." | | Judge Andrew Kleinfeld |
