i think i know what i am talking about , but mixed something up .. :-)
i am more interested in the extended info of the volume, but over a bulk interface with formatted output.
especially the statistic stuff is very important ....


ep14:~ # vos examine root.afs -extend
root.afs                          536870912 RW          7 K used 5 files On-line
    afsfs01 /vicepba
    RWrite  536870912 ROnly  536870913 Backup          0
    MaxQuota       1024 K
    Creation    Sat Dec 29 00:28:49 2001
    Last Update Wed Jan 14 19:33:56 2004
    0 accesses in the past day (i.e., vnode references)

                      Raw Read/Write Stats
          |-------------------------------------------|
          |    Same Network     |    Diff Network     |
          |----------|----------|----------|----------|
          |  Total   |   Auth   |   Total  |   Auth   |
          |----------|----------|----------|----------|
Reads     |        0 |        0 |        0 |        0 |
Writes    |        0 |        0 |        0 |        0 |
          |-------------------------------------------|

                   Writes Affecting Authorship
          |-------------------------------------------|
          |   File Authorship   | Directory Authorship|
          |----------|----------|----------|----------|
          |   Same   |   Diff   |    Same  |   Diff   |
          |----------|----------|----------|----------|
0-60 sec  |        0 |        0 |        0 |        0 |
1-10 min  |        0 |        0 |        0 |        0 |
10min-1hr |        0 |        0 |        0 |        0 |
1hr-1day  |        0 |        0 |        0 |        0 |
1day-1wk  |        0 |        0 |        0 |        0 |
> 1wk     |        0 |        0 |        0 |        0 |
          |-------------------------------------------|

    RWrite: 536870912     ROnly: 536870913
    number of sites -> 4
       server afsfs01 partition/vicepba RW Site
       server mfgmzafsc01 partition /vicepaa RO Site
       server afsfs01 partition /vicepaa RO Site
       server afsfs02 partition /vicepda RO Site


Sven

-------------------------------------------------------------------------------------------------------------------------
Dept. A153,  STG/ISC EMEA AIS Strategy and Architecture
Development Leader Stonehenge
IBM intranet ---> http://w3.ais.mainz.de.ibm.com/stonehenge/
internet ---> http://www-5.ibm.com/services/de/storage/stonehenge.html
Phone (+49)-6131-84-3151
Fax      (+49)-6131-84-6708
Mobil   (+49)-171-970-6664
E-Mail : [EMAIL PROTECTED]



Chaskiel M Grundman <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]

21/02/2005 20:07

To
[email protected]
cc
Subject
Re: [OpenAFS-devel] some requests





--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.

Reply via email to