On Tue, Jun 14, 2011 at 6:08 PM, Andrew Deason <[email protected]>wrote:
> On Tue, 14 Jun 2011 17:56:44 -0400 > Aaron Knister <[email protected]> wrote: > > > The issue can be mitigated if the cache size is raised to the value of > > roughly half of the physical memory in the given system. The issue > > appeared somewhere between Solaris 10 "u8" and "u9." > > "Mitigated" as in, it goes away entirely, or is less likely to occur, or > ... ? > It's significantly less likely to occur. I only had it occur twice as compared to the 20+ times it did not occur and both times I was concatenating large files in my AFS home directory to test with. > > > I've reproduced the problem using OpenAFS 1.4.14.1, 1.5.78 and > > 1.6.0pre6 and a Solaris 10 "u8" system with all of the latest patches > > applied. > > Do you mean u9? "between u8 and u9" I would take to mean that the issue > does not exist on u8, so... Or do you mean it happens on u8 only when > you've applied certain patches? > Stock u8 doesn't have the issue. There's a patch in there somewhere that after applying causes the issue. Figuring out which patch would be a real headache. > > Do you know what the cache size and chunk size was in these situations? > (You can get these from 'cmdebug -cache', in the future) > bash-3.2# /usr/afsws/bin/cmdebug -cache -servers localhost Chunk files: 1953 Stat caches: 2929 Data caches: 1953 Volume caches: 200 Chunk size: 262144 Cache size: 499968 kB Set time: no Cache type: memory Thanks! > > -- > Andrew Deason > [email protected] > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Aaron Knister Systems Administrator Division of Information Technology University of Maryland, Baltimore County [email protected]
