Running iozone -a on a recent protos branch build (probably trunk as
well), with a 25 MB cache, I usually see a afs lockup at 32768/8192,
with a 10MB cache, at 16384/16384.
After that hang, kdump -global shows:
afs_mariner = 0x0
afs_freeVCList = 0xe0b08c50 XXX
freeDCList = 0x978
freeDCCount = 0x92a (2346)
discardDCList = 0xffffffff
discardDCCount = 0x0 (0)
freeDSList= 0xe105b370 XXXX
cacheInode = 0xc (12)
volumeInode = 0xd (13)
cacheDiskType = 0x0 (0)
afs_indexCounter = 0x0.BA80B (0.763915)
afs_cacheFiles = 0x9c4 (2500)
afs_cacheBlocks = 0x2710 (10000)
afs_cacheStats = 0x2710 (10000)
afs_blocksUsed = 0x2680 (9856)
afs_blocksDiscarded = 0x0 (0)
afs_fsfragsize = 0xfff
afs_WaitForCacheDrain = 0x1 (1)
afs_CacheTooFull = 0x1 (1)
pagCounter = 0x2 (2)
So, it appears there is something happening during a cache flush that's
resulting in deadlock perhaps. It does not recover from this hang. Rest
of the machine appears fine, but any access to afs blocks forever.
I do not know if this is related to the other problems I was seeing with
our samba servers, but the lockup feel is the same.
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: [EMAIL PROTECTED]
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
_______________________________________________
OpenAFS-devel mailing list
[EMAIL PROTECTED]
https://lists.openafs.org/mailman/listinfo/openafs-devel
