Pile of Dross

Response from SC support person last night – probable CASTOR config problem, its been handed over to CASTOR support, no repsonse or change of behaviour yet
Enabled more sites in R-GMA database, bounced one odd one to R-GMA developers
Query came in from Spain about using our SE for CMS Production work, said okay but cc’d UK CMS as it could conflict with SC3 activity, which started involved discussion. In course of this, discovered that CMS has 4TB of tape allocated for their uses and want to write 18TB, having written 4TB so far. So worked out how to cut off a vo from tape access, not pretty but it’ll work – change the write preference on the link from the :tape@osm to tape pools to 0, data transfer then dies with a no suitable write pools found error. Also we’ve decided that publishing negative numbers when an experiment has over used its space is the right thing to do, so removed the lines I’d put into the info provider scripts to stop them publishing negative numbers, noted that this breaks GSTAT.
CMS have got temporary allocation from User Board to have a tape allocation of 25TB.
Considering writing SURE tests for experiment using too much tape

Trackback This Post | Subscribe to the comments through RSS Feed