Difference: CernLbdDiskManagement (7 vs. 8)

Revision 82010-12-13 - RobLambert

Line: 1 to 1
 
META TOPICPARENT name="CernLbdDiskSpace"

CernLbdDiskManagement

This is the LHCb CERN LBD group page describing the management of locally available disk space

Line: 9 to 9
  The instructions here are in addition to the instructions on CernLbdDiskSpace.
Added:
>
>
The scripts for management, and other things are kept in backed up afs space: /afs/cern.ch/lhcb/group/lbd/scripts/, which is softlinked to /afs/cern.ch/project/lbcern/scripts
 

z5:cernlbd

z5:cernlbd holds the access list for the 1TB disk space.

Line: 29 to 31
 afs_admin set_quota /afs/cern.ch/project/lbcern/vol1 100G #change the quota of a volume fs sa /afs/cern.ch/project/lbcern/vol2 z5:cernlbd write #give the right permissions afs-admin list_project lbcern #to list the amount of space for the project
Changed:
<
<
python ~rlambert/public/LBD/check1TB.py #to check the usage and the usage per user
>
>
python /afs/cern.ch/project/lbcern/scripts/check1TB.py #to check the usage and the usage per user
 

z5:cernlbd is the access list for this volume. All users should make directories with their user name. If there is some top-level directory without a user name it should be moved/deleted.

Line: 71 to 73
  To find out the used quotas of all users:
Changed:
<
<
python  ~rlambert/public/LBD/check30TB.py
>
>
python  /afs/cern.ch/project/lbcern/scripts/check30TB.py
  Then to get the list of files:
Line: 81 to 83
  It is not clear how we can check quickly what is on lhcbt3 from central productions, and which user staged any individual file into the pool is unknown.
Changed:
<
<
python  ~rlambert/public/LBD/check30TB.py --data >year< --MC
>
>
python  /afs/cern.ch/project/lbcern/scripts/check30TB.py --data >year< --MC
  This will take a very long time, probably.
Line: 97 to 99
  Or remove a big list with:
Changed:
<
<
~rlambert/public/LBD/lhcbt3_rm.py <username or directory or file with a list in it>
>
>
/afs/cern.ch/project/lbcern/scripts/lhcbt3_rm.py <username or directory or file with a list in it>
  Removing a user file potentially deletes the file forever, so it's nice to get the users to do that themselves, but any centrally produced or grid-resident file is by definition backed-up and can be removed arbitrarily.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback