Community
Participate
Working Groups
gLite storage elements implement a (new in SRMv2.1 AFAIK) feature called "space tokens". They are a way of reserving space on a storage element. Actually some LCG VOs now do NOT allow writing on a SE if you do not have a space token! (ie, 0 reserved space if you come without such token). So we should evaluate how to handle space tokens in our implementations... Some info about Atlas use of space tokens: https://twiki.cern.ch/twiki/bin/view/Atlas/SpaceTokens As cross reference see the discussion in Bug #246484 Sander's usecase: ------------------ I'm not a specialist, but here is what I understand so far: - Atlas has assigned space tokens to all VO disk space. - All SRM storage operations need: -s ${SPACETOKEN} - I know what the space token is, or at least I can find out. - In case I try to do a storage operation without the above it will fail. - The failure message is: "no space left on device". The consequences are that my job fails because: - I have the following items in my stage-out: myJob.sterr, myJob.stout, myNTuple.root - These files can only be copied to an SE (right?). - I need these files, otherwise my jobs are useless. - The SE expects a space token, but I can't provide it. * Options that come to mind are: - Provide it during the SE mount and propagate from there. - Provide it in myJob.jsdl - As a result, my job hangs in the running state. * It infinitely tries to copy the files out. * The SE returns "no space left on device". Those are the details of my use case. --------------------------
