| |
 |
 |
 |
 |
 |
 |
 |
|
|
 |
|
|
| |
Quota
and Usage Statistics
The USCMS
Tier 1 Facility provides several file sytems for its users. These file
sytems are configured in different ways for different purposes.
Information is provided below on purpose and configuration differences,
quota and usage statistics, instructions on how to check your quota and
options available to you if you should run out of quota.
These web pages are updated at 7AM.
All requests for space must be approved by Dan Green or Chris Tully.
/uscms
Snapshots for /uscms are daily starting at 18:00 and kept for 4 days.
(for details see Backup/SnapShot )
Purpose: Home areas, area small quota, backed up to tape
- Stats sorted
by usage
- Stats sorted
by quota limit set
- Stats
sorted by percentage of limit used
/uscms_data/d1
No tape backups
No snapshots
Purpose: Data area with quotas (large for LPC
groups), not backed up to tape
- Stats
sorted by usage
- Stats
sorted by quota limit set
- Stats
sorted by percentage used
/uscmst1b_scratch/lpc1
No tape backups
No snapshots
Purpose: Data area WITHOUT
quota for LPC groups, not backed up to tape
- Stats
usage
Checking your quota usage:
Users can use the UNIX "quota" command to check their disk/quota
usage. The output includes information on ALL nfs mounted file systems
even those that may not have quotas set.
An example:
<> quota -s
quota: Error while getting quota from cmspnfs:/cms for 1291: Invalid argument
quota: Error while getting quota from cmsstor37:/uscmst1/prod for 1291: Invalidargument
Disk quotas for user lisa (uid 1291):
Filesystem blocks
quota limit grace files
quota limit grace
blue2.fnal.gov:/uscmst1b_scratch/lpc1
8826G 0
14336G
944k
0 0
blue2.fnal.gov:/uscms_data/d1
32 0
20480M
8749k
0 0
blue2.fnal.gov:/uscms
864 0
2048M
41
0 0
The "-s" option tells the quota command to try to use units for showing the usage/limit output.
The errors in the output are normal. The two pertinent fields in this
output are the first and third. The first shows how much disk is being
used and the third shows what your limit is set to. As you can see in
the example /uscmst1b_scratch/lpc1 shows a very high limit for this
user. This is due to the fact that a default quota was set on this
file system so we could use the quota facility to track individual
users disk usage without actually limiting any one user or groups
usage.
There is another useful option to the quota command which is the "-q".
This option tells the quota command to only print information about
file systems where you are over quota.
What to do if you exceed your
quota limit:
- Remove uneeded files
- Utilize the 3DayLifetime area in
/uscmst1b_scratch/lpc1/3DayLifetime. As the name implies any data
stored here is automatically removed after 3 days.
- Copy data to dcache.
- If you are a member of one of
the LPC groups, you can utilize
the storage areas allocated to that group. If you find you can not access the
area allocated to the group you are a member of, send email to the
coodinator listed on the above referenced web page to request access.
These LPC group areas are located at:
- /uscms_data/d1/<group
name> (quota limit set; ksu to the physics group user
before writing)
- /uscmst1b_scratch/lpc1/<group
name>
- /uscms_scratch/<group
name>
- If all of the above are not sufficient,
you can request more disk
space.
|
|
|
|
|
|
|
| |
|
|
|
