OUTDATED: Policies concerning the /store/temp and /store/unmerged directories
The following table is outdated. All relevant policies should be taken from DMWMPG_Namespace twiki.
/store/unmerged and /store/temp are special directories which hold temporary files. They can be cleaned up automatically by the sites to free up disk space, but live within the Ops disk allocation at the sites. They should be
T0D1 (disk only). The access permissions to the directories is listed below following the VOMS role setup defined here:
CompOpsPoliciesVOMSRoles:
directory |
description |
roles with write permission |
accessible through srm (YES/NO) |
min file retention time |
/store/unmerged |
legacy directory holding temporary files and logArchive tarballs |
t1production, production, hit1production, h1production |
NO (logCollect jobs archive logArchives to CERN, but srm access still would be nice) |
2 weeks |
/store/temp |
new main directory for temporary files |
NO ACCESS |
NO |
2 weeks |
/store/temp/prod |
new main directory for temporary production files |
t1production, production, hit1production, h1production |
NO |
2 weeks |
/store/temp/user |
new main directory for temporary user files |
every CMS VOMS proxy |
YES (asynchronous stageout) |
1 week, sites can fail writing to area if it holds more than 20 TB |
The srm accessibility should guarantee that what really needs access through srm is defined. Of course all other areas would benefit from SRM accessibility.