Here's how to do the tracking-only trees (from our active quota file).  Enabling it causes no problems.  We actually turn on certain tracking quotas in the middle of the day from time to time.

#Qtree Quotas
#---------------------------------------------------------------------------------------------
#Target                                Type    Disk    Files   Thold   Sdisk   Sfile   Comment
#---------------------------------------------------------------------------------------------

<------------snip
/vol/perforce/ActiveXContainer         tree      -
/vol/perforce/ASIC                     tree      -
/vol/perforce/ATC                      tree      -
/vol/perforce/CodeMart                 tree      -
/vol/perforce/ComponentWorks           tree      -
/vol/perforce/CVI                      tree      -
/vol/perforce/DAQ                      tree      -
/vol/perforce/DAQConfig                tree      -
/vol/perforce/DevSuite                 tree      -
<------------snip

The output of the quota report will look like the following.  Notice that the "limit" fields for all quotas are "-" indicating no limit.  However, it does give size and number of files (which we find useful)

hades> quota report
                                         K-Bytes           Files
Type       ID    Volume    Tree  Used     Limit    Used    Limit   Quota Specifier
----- -------- -------- -------- -------- -------- ------- ------- ---------------
<------------snip
tree         1 perforce ActiveXContainer    104340         -    5630       - /vol/perforce/ActiveXContainer
tree         2 perforce     ASIC  25975900         -   97173       - /vol/perforce/ASIC
tree         3 perforce      ATC  17604848         -  109831       - /vol/perforce/ATC
tree         4 perforce CodeMart   4980056         -   35261       - /vol/perforce/CodeMart
tree         5 perforce ComponentWorks   2085444         -   34330       - /vol/perforce/ComponentWorks
tree         6 perforce      CVI   9946108         -   86842       - /vol/perforce/CVI
tree         7 perforce      DAQ  18813660         -  223765       - /vol/perforce/DAQ
tree         8 perforce DAQConfig   1026752         -   10632       - /vol/perforce/DAQConfig
tree         9 perforce DevSuite     97776         -    1524       - /vol/perforce/DevSuite
<------------snip


Jeff Mery - MCSE, MCP
National Instruments

-------------------------------------------------------------------------
"Allow me to extol the virtues of the Net Fairy, and of all the fantastic
dorks that make the nice packets go from here to there. Amen."
TB - Penny Arcade
-------------------------------------------------------------------------



Lori Barfield <itdirector@gmail.com>
Sent by: owner-toasters@mathworks.com

11/10/2005 02:10 PM

To
John Stoffel <john.stoffel@taec.toshiba.com>, toasters@mathworks.com
cc
Subject
Re: howto document for initial volume architecting?





On 11/10/05, John Stoffel <john.stoffel@taec.toshiba.com> wrote:
>
> Jerry> .... i guess today i'm going to be adding up directory sizes
> Jerry> with a massive find -prune loop.  (or is there a better way?)

> What's I'd do is setup a quotas file for all your qtrees, but put in
> an empty quota.  Then you turn on quotas, wait for them to initialize,
> and then run a quota report.  Works very well.

i looked at the man page and there are no hints about how
to add an empty quota.  i don't want to enable quotas and
suddenly put everyone in outage because i don't know the
right syntax.  may i ask toasters for an example command,
please?  i'll try it first on a less-busy qtree, and if all goes
well, will do it everywhere.

btw, i received the private suggestion of running a df from
inside a snapshot for counting space used.  it was such
a good idea i wanted to share it.  of course, that's not a
proper way to monitor usage on a filer, but it got my doc
effort off the ground this morning.  thank you, toasters. :)


...lori