...
The data are also loaded to an Oracle database and are accessible through a web application (currently in test stage):
The disk space usage values are stored in Oracle. A key-value together with the date is recorded. The following key names are used:
Key | Description |
---|---|
xrootd_freeGB_<server> | free disk space in GB for <server>, e.g.: xrootd_freeGB_wain021 |
xrootd_diskGB_<server> | disk size in GB for <server> |
xrootd_usedGB_<server> | used disk space in GB for <server>, (xrootd_diskGB_server> - xrootd_freeGB_<server>) |
xrootd_all_freeGB | free disk space in GB summed over all xrootd data servers. |
xrootd_all_diskGB | disk size in GB summed over all xrootd data servers. |
xrootd_all_usedGB | used disk space in GB summed over all xrootd data servers, (xrootd_all_diskGB - xrootd_all_freeGB) |
...
The foramt of date is YYYYMMDDTHHMMSS, e.g. 20080712T123258. The totalSpace and freeSpace are in GB. The inode info is only shown for serves that use the ufs file system (all sulkies) but not for the servers that employ zfs.
In order to calculate the free disk and total disk space of the xrootd cluster the values, taken around the same time , for all data servers have to be summed.
The disk space usage values are stored in Oracle. A key-value together with the date is recorded. The following key names are used:
...
Key
...
Description
...
xrootd_freeGB_<server>
...
free disk space in GB for <server>, e.g.: xrootd_freeGB_wain021
...
xrootd_diskGB_<server>
...
disk size in GB for <server>
...
xrootd_usedGB_<server>
...
used disk space in GB for <server>, (xrootd_diskGB_server> - xrootd_freeGB_<server>)
...
xrootd_all_freeGB
...
free disk space in GB summed over all xrootd data servers.
...
xrootd_all_diskGB
...
summed
...
.
...
xrootd_all_usedGB
...