[OpenAFS-devel] Proposed enhancements to volinfo command

Phil.Moore@morganstanley.com Phil.Moore@morganstanley.com
Thu, 7 Mar 2002 12:05:53 -0500


I recently discovered that the volinfo command can extract some very
interesting information from the volume header that is not obtainable
through any vos command, information I need for some important usage
audits we're developing.

In particular, volinfo will show the dayUseDate, which is the
timestamp of the last access to the volume.  This is not obtainable
through any of the vos command interfaces.  So, I'm reworking my
volume audits to use volinfo, rather vos listvol, to get this data.

However, when processing an entire /vice partition, volinfo will
simply abort when it encounters a volume header it can't read.
Compare this to vos listvol, which will simply report the fact that
one or more volumes are not attached, and continue to process the rest
of the headers in a given partition.

This makes it difficult to develop a scalable audit tool, since it
should be obvvious I don't want to call listvol once for each
individual volume.

I'm working on a patch for this, and I propose to treat unattached
volume headers as non-fatal errors when processing an entire
partition, or an entire server.  Thus, the behavior will be analagous
to that of vos listvol.  It will only be a fatal error when the volume
ID is give on the command line (i.e. you asked about that specific
volume).

Question: will this break anyone's code somewhere out there?  

I can make it 100% backwards compatible, by adding a command line
argument (-allowunattached?  kinda long) to enable the change, but is
this necessary?

Opinions?