INFN Disk Servers

fcdfdata009, fcdfdata010, fcdfdata011. Three 1.8TB fileservers (5.4TB total) were part of the original CAF static data disk poool. See Datasets on CAF list.
4 fileservers, 1.8 TB each, to be used for data stripping output etc.

fcdfdata013 (May 2002) [ STATUS. ]

Assigned to Top group, managed by Patrizia Azzi and Andrea Castro

fcdfdata014 (May 2002) [ STATUS. ]

SAM station cdf-cat used for skim managed by Donatella Lucchesi and Francesco Delli Paoli

fcdfdata015 (May 2002) [ STATUS. ]

Assigned to EW group, managed by Tommaso Dorigo and Andrea Messina

fcdfdata026 (Fall 2002) [ STATUS. ]

Assigned to B group, managed by Stefano Giagu and Giovanni Punzi

2 fileservers, 5 TB each, purchased in 2003, operational by end of January 2004 assigned

fcdfdata103: 5TB as personal icaf & scratch area [ STATUS. ] All INFN users have 200GB quota on this disk.
fcdfdata105: 5TB filesever in the dCache pool. As of Feb 2004 this is used to gurarantee golden data set status for compressed B-Charm dataset.

As of Februrary 2004 there are seven 1.8TB and two 5TB file servers for a total of 22.6 TB.

50% is for internal usage, 50% for hosting data sets of common CDF utilisation according to CDF policy

Policies and Access tools:

icaf/scratch
- Access to icaf/scratch server is made under the guidelines of the CAF user manual, e.g. with Igor's icaf tools from offsite.
- Access to icaf/scratch server from within CAF jobs has to be done using rcp. From outside the CAF, using ftp. Always with a proper kerberos ticket. (kerberised) rsh to the file server is only possible from a CAF job and using the -N qualifier.
- There is no backup, and no automatic deletion of old files.
- Nevertheless please cleanup unused files, the total assigned quota is always larger then the disk, user should not "live at the edge of their quota" and should not leave large dead files around once their work is finished.
- As of today every INFN user should have 50/100 GB of soft/hard quota on icaf/scratch area (twice as much as common CDF'ers).
static file servers
- Static file servers (fcdfdata013/15/26) are managed via the cdfdata account.
- There is no other user on these machines but cdfdata, cdfdata owns all the local disk with no quota
- Data is managed by users who have access by having their principal listed in cfdata's .k5login. This list will always include me (Donatella) for management purpose (i.e. adding/removing others as disk areas are assigned around).
- Local disk is not NFS mounted to worker nodes, access is only via network.
- Data is put/retrieved according to same rules as icaf/scratch, with the obvious warning of specifying -l cdfdata in kerberised commands. From CAF jobs is possbile to use rcp, rsh and rootd (rootd is the preferred data access method), from offsite is possible to use rootd and/or ftp.
data access
- All file servers data are accessible via anonymous ftp. See Caf User's Guide
- When accessing a large data set that sits on one only file server, care must be taken to avoid overloading the server with network access requests by tens and tens of concurrent processes (especially if using the italy queue)., even rootd may fail at that point. In this case it is recommended to use fcp to copy each file to the local disk before opening it. Here is an example of using fcp around anonymous ftp to achieve this.

Donatella Lucchesi

Last modified: Wed Nov 22 19:18:39 MET