--On Monday, February 21, 2005 18:43:47 +0100 Sven Oehme <[EMAIL PROTECTED]> wrote:
> but the VLDB output is the output i would be most interested in .. > especially if you like to export this data to use it in excel or other > tools .. Do you really care about the vldb part? % vos exa user.cg2v volser> user.cg2v 1970723513 RW 179994 K On-line volser> VICE16.FS.andrew.cmu.edu /vicepb volser> RWrite 1970723513 ROnly 0 Backup 1970723515 volser> MaxQuota 200000 K volser> Creation Thu Aug 6 17:18:21 1992 volser> Last Update Mon Feb 21 13:48:15 2005 volser> 1658 accesses in the past day (i.e., vnode references) vldb> RWrite: 1970723513 Backup: 1970723515 vldb> number of sites -> 1 vldb> server VICE16.FS.andrew.cmu.edu partition /vicepb RW Site the information tagged 'volser' will be present in vos listvol -long (which is a bulk interface) the information tagged 'vldb' will be present in vos listvldb (which works either singly or in bulk; it has optional -server -partition switches) I think you may misunderstand what the vldb is precisely. The vldb (vlserver) is a "directory service" that maps volume names to and from ids and also identifies the set of fileservers that the volume allegedly exists on. The volserver is a volume-level management interface. Most volume metadata is stored on the fileserver(s) that the volume is resident on and is accessible via the volserver interface. The 'vos' program utilizes both of these services, but they are distinct.
p7sBWQq5QlADL.p7s
Description: S/MIME cryptographic signature
