Hi,
I'm trying to keep track of which volumes of software are
used in our environment. I've come across an annoying bug in
the statistics reporting, however.
If a volume is accessed at all during any particular 24-hr period, its
access count goes up accordingly. However, at the standard
midnight-GMT turnaround point, it doesn't go back to zero
automatically, at least according to vos examine. It will stay at the
previous 24-hour count *indefinitely* if untouched. But, as soon as it
is accessed once again, its count resets correctly as if it were truly
at zero and just freshly accessed. As if that later access 'kicked' it
back into sanity. Here's an example:
(servers obscured since I'm not sure I'm allowed to announce our cell.)
furlong:~[655]% vos ex mac_71.msoffice.003
mac_71.msoffice.003 536875560 RW 151914 K On-line
XXX1.jpl.nasa.gov /vicepj
RWrite 536875560 ROnly 536875561 Backup 536875562
MaxQuota 185000 K
Creation Fri Jan 19 15:51:35 1996
Last Update Fri Jan 19 18:38:46 1996
[note it hasn't been touched in ages]
95563 accesses in the past day (i.e., vnode references)
[it's been reading '95563' ever since I've been keeping track of it;
vos ex -exntended shows all these accesses are reads]
RWrite: 536875560 ROnly: 536875561
number of sites -> 3
server XXX1.jpl.nasa.gov partition /vicepj RW Site
server XXX1.jpl.nasa.gov partition /vicepj RO Site
server XXX2.jpl.nasa.gov partition /vicepj RO Site
Ok, so I take a closer look:
furlong:~[656]% fs mkm msoffice mac_71.msoffice.003
[this doesn't cause any change in access count]
furlong:~[658]% ls msoffice
[buncha windoze garbage deleted; just forcing accesses]
furlong:~[659]% vos ex mac_71.msoffice.003
mac_71.msoffice.003 536875560 RW 151914 K On-line
XXX1.jpl.nasa.gov /vicepj
RWrite 536875560 ROnly 536875561 Backup 536875562
MaxQuota 185000 K
Creation Fri Jan 19 15:51:35 1996
Last Update Fri Jan 19 18:38:46 1996
2 accesses in the past day (i.e., vnode references)
[***^*** 2! So it's as if it were '0' internally *somewhere*, and it's
counting up from there.]
>From another example, I can assure you it will read 2 indefinitely
from now on. Does this still occur in AFS3.4a? Is it a known bug?
Known "feature"? Can't be, can it? It does say, "in the past day."
We'd like to keep track of volume accesses without this as a hindrance.
Any help appreciated. Thanks,
Daniel Bromberg, Co-op
[EMAIL PROTECTED]
M/S 171-300 (818) 393-3872
FAX: (818) 393-5009
Metrics Engineer, EIS project
Jet Propulsion Laboratory
4800 Oak Grove Dr.
Pasadena, CA 91109
