CERN Accelerating science

This website is no longer maintained. Its content may be obsolete. Please visit http://home.cern/ for current CERN information.

CERN home pageCERN home pageDocuments by ReferenceDocuments by ReferenceCNLsCNLsYear 2002Year 2002Help, Info about this page

Contents
Index

Editorial Information
Editorial
If you need help
Announcements Physics Computing Desktop Computing Internet Services and Network Scientific Applications and Software Engineering The Learning Zone User Documentation
Previous:Data Services Group Activities and Plans
Next:Desktop Computing
 (If you want to print this article)



AFS Project Space Administration - New Project Quota Structure

Rainer Többicke , IT / Data Services


Abstract

afs_admin is used to manage AFS disk space.


With the new 'afs_admin' command introduced last summer a revised structure has been put in place allowing for refined control of AFS project space allocation. 'afs_admin' is the tool used by AFS project space administrators to manage experiment/project disk space, as well as scratch/work space given out to individual users from the experiments quota.

Formerly, only two distinct categories of AFS project space ("backed-up" and "non-backed-up") were available. They were controlled by a single "project quota" for the experiment/project limiting the aggregate quota of AFS volumes in the project. AFS volumes in the "backed-up" category would typically start with 'p.projectname...' and in the "non-backed-up" category with 'q.projectname...'.

In the new structure:

  1. Quota for each category can (would normally) be specified individually.
  2. A new category "user-scratch" has been added: meant as scratch work space for individual users, usually implemented on cheap disks. In case the disks or the servers holding them fail, the data may be lost, as there are no backups. This space is therefore unsuitable for data which cannot be re-created or recovered by other means. Scratch volumes are created using the 'afs_admin create_scratch' command. Volumes in this category start with 's.projectname...', and will have a directory name of ~userid/scratchN, N=0,1,2,...
  3. The previous categories remain as before: 'q.projectname...' volumes are for data which will not be backed up and should therefore be re-creatable by other means, 'p.projectname...' and 'u.projectname.userid.X' volumes (accessible under ~userid/wN, N=0,1,2,...) are backed-up daily to tape, back-ups are kept for about a year at increasingly spaced intervals. Data in these two categories are placed on highly reliable servers and disks.
The 'afs_admin list_project' and 'afs_admin list_quota' now list the project's AFS volumes or its "project quota" under the different categories separately - provided distinct values have been assigned - with headings 'projectname_q' or 'projectname_s', or even 'projectname_p'. Additionally, it is now possible to restrict the output of 'afs_admin list_project' to volumes of a certain category by appending a '_p', '_q' or '_s' to the project name, e.g. 'afs_admin list_project atlas_q'.


For matters related to this article please contact the author.
Cnl.Editor@cern.ch


CERN-CNL-2002-003
Vol. XXXVII, issue no 3


Last Updated on Tue Dec 10 13:41:47 CET 2002.
Copyright © CERN 2002 -- European Organization for Nuclear Research