IN PROGRESS

DCACHE FNAL (as of October 26th, 2007)

  1. srmStatusOfGetRequest returns an inconsistent return code at request level This has been FIXED : - URGENT
    srmStatusOfGetRequest https://srm-devel.desy.de:8443/srm/managerv2 requestToken=-2147203007 SURL[srm://srm-devel.desy.de:8443/srm/managerv2?SFN=///pnfs/desy.de/data/dteam/20071016-132958-14526-0.txt] 
    It returns:
    sourceSURL0=srm://srm-devel.desy.de:8443/srm/managerv2?SFN=///pnfs/desy.de/data/dteam/20071016-132958-14526-0.txt fileSize0=2713 returnStatus.explanation0=AsyncWait returnStatus.statusCode0=SRM_REQUEST_INPROGRESS estimatedWaitTime0=4 returnStatus.explanation=" at Tue Oct 16 13:33:03 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_PARTIAL_SUCCESS
    
  2. Put and Get requests return SRM_FAILURE instead of SRM_NOT_SUPPORTED if the protocol specified is not supported This has been FIXED
  3. srmGetSpaceTokens returns SRM_SUCCESS instead of SRM_INVALID_REQUEST if the space token description provided does not refer to any existing space token description This has been FIXED
  4. srmPrepareToPut returns SRM_FAILURE instead of SRM_NOT_SUPPORTED at request level in case the protocol specified is not supported. SRM_FAILURE should be returned only at file level in this case This has been FIXED
  5. srmPrepareToPut returning SRM_AUTHORIZATION_FAILURE instead of SRM_AUTHENTICATION_FAILURE if client is not authenticated. This has been FIXED
  6. srmStatusOfGetRequest changes over time as in the following. This has been FIXED
    srmStatusOfGetRequest https://fapl110.fnal.gov:8443/srm/managerv2 requestToken=-2147177526 SURL[srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-0.txt srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt] 
    It returns:
    sourceSURL0=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-0.txt fileSize0=2702 returnStatus.explanation0=Ready returnStatus.statusCode0=SRM_FILE_PINNED estimatedWaitTime0=1 remainingPinTime0=3577 transferURL0=gsiftp://fapl117.fnal.gov:2811///testers/NULL/20070918-143832-23668-0.txt sourceSURL1=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt fileSize1=1706 returnStatus.explanation1=Ready returnStatus.statusCode1=SRM_FILE_PINNED estimatedWaitTime1=1 remainingPinTime1=3577 transferURL1=gsiftp://fapl117.fnal.gov:2811///testers/NULL/20070918-143832-23668-1.txt returnStatus.explanation=" at Tue Sep 18 07:39:08 CDT 2007 state Pending : created" returnStatus.statusCode=SRM_SUCCESS
    
    srmAbortFiles https://fapl110.fnal.gov:8443/srm/managerv2 requestToken=-2147177526 SURL[srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt] 
    It returns:
    surl0=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt returnStatus.explanation0=Canceled returnStatus.statusCode0=SRM_SUCCESS returnStatus.statusCode=SRM_SUCCESS
    
    srmStatusOfGetRequest https://fapl110.fnal.gov:8443/srm/managerv2 requestToken=-2147177526 SURL[srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-0.txt srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt] 
    
    It returns:
    sourceSURL0=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-0.txt fileSize0=2702 returnStatus.explanation0=Ready returnStatus.statusCode0=SRM_FILE_PINNED estimatedWaitTime0=1 remainingPinTime0=3564 transferURL0=gsiftp://fapl117.fnal.gov:2811///testers/NULL/20070918-143832-23668-0.txt sourceSURL1=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070918-143832-23668-1.txt fileSize1=1706 returnStatus.explanation1=Canceled returnStatus.statusCode1=SRM_ABORTED estimatedWaitTime1=1 remainingPinTime1=0 transferURL1=gsiftp://fapl117.fnal.gov:2811///testers/NULL/20070918-143832-23668-1.txt returnStatus.explanation=" at Tue Sep 18 07:39:08 CDT 2007 state Pending : created" returnStatus.statusCode=SRM_ABORTED
    
  7. srmAbortFiles fails after an srmPrepareToGet that is still queued with a strange message This has been FIXED - It was due to the system being restarted
     srmAbortFiles https://fapl110.fnal.gov:8443/srm/managerv2 requestToken=-2147185533 SURL[srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070914-150230-31679-1.txt] 
    It returns:
    surl0=srm://fapl110.fnal.gov:8443/srm/managerv2?SFN=//pnfs/fnal.gov/data/testers/NULL/20070914-150230-31679-1.txt returnStatus.explanation0="FAILED:  at Fri Sep 14 08:04:00 CDT 2007 state Failed : No Route to cell for packet {uoid=<1189775040301:22963>;path=[>PinManager@local];msg=Tunnel cell >PinManager@local< not found at >dCacheDomain<}" returnStatus.statusCode0=SRM_FAILURE returnStatus.statusCode=SRM_SUCCESS
    
  8. Put status changing with time This has been FIXED - This was due to NDGF restarting their dCache services
     srmPrepareToPut https://srm2.ndgf.org:8443/srm/managerv2 fileRequests.SURL[srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt] fileRequests.expectedFileSize[2702] desiredPinLifeTime=720 desiredFileStorageType=PERMANENT targetSpaceToken=65360 retentionPolicy=CUSTODIAL accessLatency=NEARLINE transferProtocols[gsiftp rfio] 
    It returns:
    requestToken=-2145921900 SURL0=srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt returnStatus.explanation0=" at Tue Sep 11 10:47:41 CEST 2007 state TQueued : put on the thread queue" returnStatus.statusCode0=SRM_REQUEST_QUEUED fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=14400 returnStatus.explanation=" at Tue Sep 11 10:47:41 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_REQUEST_QUEUED
    
     srmStatusOfPutRequest https://srm2.ndgf.org:8443/srm/managerv2 requestToken=-2145921900 SURL[srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt] 
    It returns: SURL0=srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt returnStatus.explanation0=" at Tue Sep 11 10:47:41 CEST 2007 state Failed : user has no permission to write into path /pnfs/ndgf.org/data/atlas" returnStatus.statusCode0=SRM_FAILURE fileSize0=2702 estimatedWaitTime0=4 remainingPinLifetime0=0 returnStatus.explanation=" at Tue Sep 11 10:47:41 CEST 2007 state Failed :  at Tue Sep 11 10:47:41 CEST 2007 state Pending : created
    RequestFileStatus#-2145921899 failed with error:[  at Tue Sep 11 10:47:41 CEST 2007 state Failed : user has no permission to write into path /pnfs/ndgf.org/data/atlas]
    " returnStatus.statusCode=SRM_FAILURE
    
     srmStatusOfPutRequest https://srm2.ndgf.org:8443/srm/managerv2 requestToken=-2145921900 SURL[srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt] 
    It returns: SURL0=srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070911-104740-6119-0.txt returnStatus.explanation0="" returnStatus.statusCode0=SRM_FAILURE fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=0 returnStatus.explanation="" returnStatus.statusCode=SRM_FAILURE
    
  9. Put operation returning SRM_FAILURE instead of SRM_INVALID_PATH. This has been FIXED
  10. Put operation returns some time SRM_REQUEST_INPROGRESS instead of SRM_REQUEST_QUEUED This has been FIXED :
    srmPrepareToPut https://ccsrmtestv2.in2p3.fr:8443/srm/managerv2 fileRequests.SURL[srm://ccsrmtestv2.in2p3.fr:8443/srm/managerv2?SFN=/pnfs/in2p3.fr/data/lhcb/20070910-164152-4219-0.txt] fileRequests.expectedFileSize[2702] desiredPinLifeTime=720 desiredFileStorageType=PERMANENT transferProtocols[gsiftp rfio] 
    It returns:
    requestToken=-2147413954 SURL0=srm://ccsrmtestv2.in2p3.fr:8443/srm/managerv2?SFN=/pnfs/in2p3.fr/data/lhcb/20070910-164152-4219-0.txt returnStatus.explanation0=" at Mon Sep 10 16:41:53 CEST 2007 state TQueued : put on the thread queue" returnStatus.statusCode0=SRM_REQUEST_QUEUED fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=14399 returnStatus.explanation=" at Mon Sep 10 16:41:53 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
  11. Space reservation of type REPLICA/ONLINE fails at BNL2: This has been FIXED
    srmReserveSpace https://dcsrmv2.usatlas.bnl.gov:8443/srm/managerv2 retentionPolicy=REPLICA accessLatency=ONLINE desiredSizeOfTotalSpace=1048576 desiredSizeOfGuaranteedSpace=1048576 desiredLifetimeOfReservedSpace=180 transferProtocols[gsiftp rfio] 
    It returns:
    requestToken=-2147480408 respRetentionPolicy=REPLICA respAccessLatency=ONLINE sizeOfTotalReservedSpace=1048576 returnStatus.explanation=" at Thu Sep 06 09:23:06 EDT 2007 state TQueued : put on the thread queue" returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
    srmStatusOfReserveSpaceRequest https://dcsrmv2.usatlas.bnl.gov:8443/srm/managerv2
    requestToken=-2147480408 
    It returns:
    respRetentionPolicy=REPLICA respAccessLatency=ONLINE sizeOfTotalReservedSpace=1048576 returnStatus.explanation="" returnStatus.statusCode=SRM_NO_FREE_SPACE
    
  12. GridFTP operation fails at SARA after a Mv: This has been fixed: due to a cleanup script at SARA - URGENT
    srmPrepareToPut https://ant2.grid.sara.nl:8443/srm/managerv2 fileRequests.SURL[$SPLIT{srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt}] fileRequests.expectedFileSize["$SPLIT{2702 }"] desiredPinLifeTime=720 desiredFileLifeTime=1800 desiredFileStorageType=PERMANENT transferProtocols[gsiftp rfio]
    It returns:
    requestToken=-2147439847 SURL0=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt returnStatus.explanation0=" at Thu Sep 06 15:08:32 CEST 2007 state Running : executing " returnStatus.statusCode0=SRM_REQUEST_INPROGRESS fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=14399 returnStatus.explanation=" at Thu Sep 06 15:08:32 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
    srmStatusOfPutRequest https://ant2.grid.sara.nl:8443/srm/managerv2 requestToken=-2147439847 SURL[$SPLIT{srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt}]
    It returns:
    SURL0=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt returnStatus.explanation0=" at Thu Sep 06 15:08:32 CEST 2007 state Ready : execution succeeded" returnStatus.statusCode0=SRM_SPACE_AVAILABLE fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=14399 transferURL0=gsiftp://ant3.grid.sara.nl:2811//pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt returnStatus.explanation=" at Thu Sep 06 15:08:32 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_SUCCESS
    
    globus-url-copy file:///etc/group gsiftp://ant3.grid.sara.nl:2811//pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt
    
    srmPutDone https://ant2.grid.sara.nl:8443/srm/managerv2 requestToken=-2147439847 SURL[$SPLIT{srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt}]
    It returns:
    surl0=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt returnStatus.explanation0=Done returnStatus.statusCode0=SRM_SUCCESS returnStatus.explanation=success returnStatus.statusCode=SRM_SUCCESS
    
    srmMv https://ant2.grid.sara.nl:8443/srm/managerv2 fromSURL=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-0.txt toSURL=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt
    It returns:
    returnStatus.explanation=success returnStatus.statusCode=SRM_SUCCESS
    
    srmPrepareToGet https://ant2.grid.sara.nl:8443/srm/managerv2 fileRequests.SURL[$SPLIT{srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt}] desiredFileStorageType=PERMANENT desiredPinLifeTime=720 transferProtocols[gsiftp rfio]
    
    It returns:
    requestToken=-2147439845 sourceSURL0=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt returnStatus.explanation0=TQueued returnStatus.statusCode0=SRM_REQUEST_QUEUED estimatedWaitTime0=1 returnStatus.explanation=" at Thu Sep 06 15:08:36 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_REQUEST_QUEUED
    
    srmStatusOfGetRequest https://ant2.grid.sara.nl:8443/srm/managerv2 requestToken=-2147439845 SURL[$SPLIT{srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt}]
    It returns:
    sourceSURL0=srm://ant2.grid.sara.nl:8443/srm/managerv2?SFN=/pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt fileSize0=2702 returnStatus.explanation0=Ready returnStatus.statusCode0=SRM_FILE_PINNED estimatedWaitTime0=1 remainingPinTime0=14218 transferURL0=gsiftp://ant3.grid.sara.nl:2811//pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt returnStatus.explanation=" at Thu Sep 06 15:08:36 CEST 2007 state Pending : created" returnStatus.statusCode=SRM_SUCCESS
    
    globus-url-copy gsiftp://ant3.grid.sara.nl:2811//pnfs/grid.sara.nl/data/dteam/20070906-150831-12214-1.txt file:///tmp/s2-file-to-get-1.12214
    
    and this last operation fails.
    
  13. Tier-1 sites involved in LHCb and ATLAS tests do not pass SRM v1 SAM tests for various reasons. Please check. This has been fixed
  14. SRM_FAILURE is returned instead of SRM_NOT_SUPPORTED when an srmReleaseFiles is invoked without specifying the request token. Actually the spec specify that the token is not mandatory. Therefore, the function should be fully implemented retrieving all TURLS belonging to the owner of the srmReleaseFiles requests and releasing them. This has been FIXED
    srmReleaseFiles https://ccsrmtestv2.in2p3.fr:8443/srm/managerv2 SURL[srm://ccsrmtestv2.in2p3.fr:8443/srm/managerv2?SFN=/pnfs/in2p3.fr/data/dteam/s-2/20070905-163150-29416-0.txt] 
    It returns:
    returnStatus.explanation="request contains no request token" returnStatus.statusCode=SRM_FAILURE
    
  15. SRM_FAILURE is returned instead of SRM_AUTHORIZATION_ERROR if a Put request with DTEAM DN is issued on an ATLAS specific path. This has been fixed
    
    srmStatusOfPutRequest https://dcsrmv2.usatlas.bnl.gov:8443/srm/managerv2 requestToken=-2147483057 SURL[srm://dcsrmv2.usatlas.bnl.gov:8443/srm/managerv2?SFN=//pnfs/usatlas.bnl.gov/data/atlas/20070904-191024-28189-0.txt] 
    It returns:
    SURL0=srm://dcsrmv2.usatlas.bnl.gov:8443/srm/managerv2?SFN=//pnfs/usatlas.bnl.gov/data/atlas/20070904-191024-28189-0.txt returnStatus.explanation0=" at Tue Sep 04 13:10:26 EDT 2007 state Failed : can not obtain turl for file:org.dcache.srm.SRMException: user`s path ////pnfs/usatlas.bnl.gov/data/atlas/20070904-191024-28189-0.txt is not subpath of the user`s root" returnStatus.statusCode0=SRM_FAILURE fileSize0=2702 estimatedWaitTime0=1 remainingPinLifetime0=0 returnStatus.explanation=" at Tue Sep 04 13:10:26 EDT 2007 state Failed :  at Tue Sep 04 13:10:25 EDT 2007 state Pending : created
    RequestFileStatus#-2147483056 failed with error:[  at Tue Sep 04 13:10:26 EDT 2007 state Failed : can not obtain turl for file:org.dcache.srm.SRMException: user`s path ////pnfs/usatlas.bnl.gov/data/atlas/20070904-191024-28189-0.txt is not subpath of the user`s root]
    " returnStatus.statusCode=SRM_FAILURE
    
    The same is true if the path does not have the correct permissions. The following test has been executed with an ATLAS cert:
    
    srmStatusOfPutRequest https://srm2.ndgf.org:8443/srm/managerv2 requestToken=-2145928544 SURL[srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070907-010611-14577-0.txt]
    It returns:
    SURL0=srm://srm2.ndgf.org:8443/srm/managerv2?SFN=/pnfs/ndgf.org/data/atlas/20070907-010611-14577-0.txt returnStatus.explanation0=" at Fri Sep 07 01:06:12 CEST 2007 state Failed : user has no permission to write into path /pnfs/ndgf.org/data/atlas" returnStatus.statusCode0=SRM_FAILURE fileSize0=2702 estimatedWaitTime0=4 remainingPinLifetime0=0 returnStatus.explanation=" at Fri Sep 07 01:06:12 CEST 2007 state Failed :  at Fri Sep 07 01:06:12 CEST 2007 state Pending : created
    RequestFileStatus#-2145928543 failed with error:[  at Fri Sep 07 01:06:12 CEST 2007 state Failed : user has no permission to write into path /pnfs/ndgf.org/data/atlas]
    " returnStatus.statusCode=SRM_FAILURE
    
    
  16. Space reservation for T0D1 and T1D1 is implemented in dCache in such a way that space is used for files put in that space and it is not released for files removed from the space. This has been FIXED
  17. When srmExtendFileLifeTime is called without specifying new pin or file lifetimes but specifying a request token, the current pin and file lifetimes for the correspondent TURLs/SURLs should be returned. dCache returns SRM_INVALID_REQUEST The specs need to be revisited :
     srmExtendFileLifeTime https://pps-srm-fzk.gridka.de:8443/srm/managerv2 requestToken=-2147306974 SURL[srm://pps-srm-fzk.gridka.de:8443/srm/managerv2?SFN=//pnfs/gridka.de/dteam/20070816-113459-29273-0.txt] 
    It returns:
    returnStatus.explanation=" requesToken is not null and newPinLifetime is null" returnStatus.statusCode=SRM_INVALID_REQUEST
    
  18. The numOfLevels=1 is always ignored during a directory listing. Only info about the directory are returned. This has been FIXED - This seems to happen only at IN2P3. - URGENT
    [lxplus214] ~ > lcg-ls -l -D srmv2 -T srmv2 srm://ccsrmtestv2.in2p3.fr:8443/srm/managerv2\?SFN=/pnfs/in2p3.fr/data/lhcb
    drwxr-xr-x  1     2     2     512 /pnfs/in2p3.fr/data/lhcb
    [lxplus214] ~ > lcg-ls -l -D srmv2 -T srmv2 srm://ccsrmtestv2.in2p3.fr:8443/srm/managerv2\?SFN=/pnfs/in2p3.fr/data/lhcb/raw
    drwxr-xr-x  1     2     2     512 /pnfs/in2p3.fr/data/lhcb/raw
    
  19. The removal of files does not always take place. It is not clear why. This has been FIXED - URGENT
  20. srmBringOnline leaves a file in NEARLINE. The file locality never goes to NEARLINE_AND_ONLINE. This has been FIXED
  21. SRM_FAILURE is returned in response for an srmMkDir operation on an already existing directory. The explanation said that the directory already existed, The correct return code is SRM_DUPLICATION_ERROR. This has been FIXED
  22. The srmRmdir functions returns SRM_FAILURE instead of SRM_NON_EMPTY_DIRECTORY at when a directory is not empty This has been FIXED
  23. A Mv operation of a file in a directory fails with SRM_INTERNAL_ERROR and other inconsistencies. This has been FIXED
  24. An Ls on a directory containing 2 files returns info about the first only. This has been FIXED - URGENT
  25. No tools provided for site administrators to reserve space statically for a VO. This has been FIXED
  26. No tools provided for site administrators to guarantee that a given pool will be used for space reservation with a given space token description. This has been FIXED
  27. No instructions to configure pools for a given token independently of the SAPath. (probably same as point 5). This has been FIXED .
  28. Documentation on how to make a link group reservable by a DN belonging to a given VO group (for instance lhcb:/lhcb/lcgprod) is missing. This has been FIXED
  29. Space reservation with retentionpolicy=REPLICA and unspecified accesslatency resolves in reservation of CUSTODIAL-NEARLINE type of space when the access latency optional parameter is not specified This has been FIXED .
    
    srmReserveSpace https://wn3.epcc.ed.ac.uk:8443/srm/managerv2 retentionPolicy=REPLICA desiredSizeOfTotalSpace=1048576 desiredSizeOfGuaranteedSpace=1048576 desiredLifetimeOfReservedSpace=1800 transferProtocols[gsiftp rfio] 
    It returns:
    requestToken=-2147352610 respRetentionPolicy=CUSTODIAL respAccessLatency=NEARLINE sizeOfTotalReservedSpace=1048576 returnStatus.explanation=" at Wed Sep 05 16:39:38 BST 2007 state TQueued : put on the thread queue" returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
    srmStatusOfReserveSpaceRequest https://wn3.epcc.ed.ac.uk:8443/srm/managerv2 requestToken=-2147352610 
    It returns:
    respRetentionPolicy=CUSTODIAL respAccessLatency=NEARLINE sizeOfTotalReservedSpace=1048576 returnStatus.explanation=" at Wed Sep 05 16:39:38 BST 2007 state Failed :  no space available" returnStatus.statusCode=SRM_NO_FREE_SPACE
    
  30. The documentation for installation and configuration does not seem to be sufficient for dCache sites This has been FIXED . Please, check here.
  31. srmGetSpaceMetadata returns at space level SRM_SUCCESS instead of SRM_SPACE_LIFETIME_EXPIRED if the lifetime of the space is expired. This has been FIXED .
  32. An srmPrepareToPut or an srmStatusOfPutRequest returns SRM_NO_FREE_SPACE at file and request level if the space specified is expired instead of returning SRM_FAILURE at file level and SRM_SPACE_LIFETIME_EXPIRED at request level, or (if the space token is no longer valid) SRM_INVALID_REQUEST at request level and SRM_FAILURE at file level. This has been FIXED .
  33. An srmPrepareToPut or an srmStatusOfPutRequest returns SRM_FAILURE at file and request level if no space of the requested class is available instead of returning SRM_NO_FREE_SPACE at file and request level or SRM_INVALID_REQUEST at request level and SRM_FAILURE at file level. This has been FIXED
  34. Space allocation does not work as foreseen by WLCG in case of CUSTODIAL-NEARLINE storage class. This has been FIXED .
  35. The explanation field becomes really long in case of retries. This has been FIXED .
  36. Tokens are case insensitive or better an srmGetRequestTokens returns SRM_SUCCESS even if the specified token does not exist. This has been FIXED
  37. An srmGetSpaceMetadata returns a negative LifeTimeLeft instead of 0 when the space is expired. This has been FIXED
  38. srmPing should return 2 key-value pairs in the otherInfo structure: backend_type=dCache and backend_version= This has been FIXED
  39. An srmBringOnline operation returns SRM_FAILURE with an explanation equal to: java.lang.NullPointerException This has been FIXED
  40. srmPrepareToPut on the same SURL with overwrite flag on succeeds instead of returning SRM_FILE_BUSY at file level. This has been FIXED
  41. srmPrepareToPut on the same SURL with overwrite flag off succeeds instead of returning SRM_DUPLICATION_ERROR at file level. This has been FIXED
  42. Filenames that are 255 characters long are not supported. The dCache limit of 199chars has been accepted by the experiments for the moment
  43. File sizes are not set and returned correctly by Put/Get/Bringonline/Copy operations. This has been FIXED
  44. SURLs start to exist only after a transfer is initiated and not after an srmPrepareToPut operation as stated by the SRM spec. The specs have been relaxed to accept this behavior
  45. A move operation on the same SURL returns SRM_FAILURE instead of SRM_SUCCESS. This has been FIXED
  46. When method is not supported the explanation contains often the following string: "handler discovery and dinamic load failedjava.lang.ClassNotFoundException:...". This has been FIXED
  47. Offset and Count are not supported in srmLs. The test asks for 1 entry with offset=1 and count=1 but all entries in the directory are returned. This has been FIXED
  48. Full listing on a (set of) file(s) with FullDetails=TRUE and NumOfLevels=0 does not return the file locality mandatory output parameter. This has been FIXED
  49. srmCopy from LBNL to FNAL in push mode fails because the FNAL server returns FILE_IN_CACHE, which is not a valid file level status for Copy. This has been FIXED .
  50. An srmReserveSpace of 1000GB returns SRM_FAILURE with an explanation of no space available instead of returning SRM_NO_FREE_SPACE or SRM_NO_USER_SPACE or SRM_EXCEED_ALLOCATION. This has been FIXED
  51. Recursive srmRmdir removes also files contained in subdirectories. This has been FIXED
  52. If a directory does not exists in the name space, a put cycle creates automatically if the dCache server has been configured to behave in this way This is not really an error since the spec do allow this behaviour. Users are recommended to always use srmMkdir to create directories before putting files in them.
  53. srmAbortFiles returning invalid file request status (SRM_ABORTED). This has been FIXED
  54. srmAbortRequest on srmPrepareToPut returns SRM_SUCCESS but srmStatusOfPutRequest at file level returns SRM_ABORTED and at request level SRM_FAILURE. The standard wants that srmStatusOfPutRequest returns in this case SRM_ABORTED at request level. The entire request must be aborted. This has been FIXED
  55. srmLs on top directory not supported (the call hungs!) This has been FIXED It returns SRM_NOT_SUPPORTED.
  56. Various MoU calls not implemented: srmGetRequestSummary, srmGetRequestTokens, srmGetTransferProtocols, srmExtendFileLifeTime This has been FIXED
  57. srmGetSpaceMetadata with no space token specified returns SRM_INTERNAL_ERROR This has been FIXED
  58. srmReleaseFiles returns SRM_RELEASED at file level instead of SRM_SUCCESS. This has been FIXED
  59. Operations take in general long time to complete (waiting time longer than 5 mins for a srmPrepareToPut/Get to return a TURL). This has been FIXED
  60. srmPrepareToPut returns SRM_REQUEST_INPROGRESS even if all TURLs have been assigned and the status at file level is SRM_SPACE_AVAILABLE. This has been FIXED

DPM CERN (as of September 20th, 2007)

  1. srmAbortFiles not returning the correct status code at file and request level. . GFAL and FTS do not check the return codes for this request. Low priority.
    
    srmPrepareToPut srm://lxdpm102.cern.ch:8446
    fileRequests.SURL["$SPLIT{srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt
    srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt}" ] fileRequests.expectedFileSize["$SPLIT{2702 1706 }"] desiredPinLifeTime=600
    desiredFileLifeTime=1800 desiredFileStorageType=PERMANENT transferProtocols[gsiftp rfio]
    It returns:
    requestToken=a1a0c403-305a-44b9-99d4-55ba5c9d4101
    SURL0=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt returnStatus.statusCode0=SRM_REQUEST_QUEUED
    SURL1=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt returnStatus.statusCode1=SRM_REQUEST_QUEUED
    returnStatus.statusCode=SRM_REQUEST_QUEUED
     
    srmStatusOfPutRequest srm://lxdpm102.cern.ch:8446
    requestToken=a1a0c403-305a-44b9-99d4-55ba5c9d4101
    SURL["$SPLIT{srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt
    srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt}" ]
    It returns:
    SURL0=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt returnStatus.statusCode0=SRM_SPACE_AVAILABLE fileSize0=0
    remainingPinLifetime0=419 remainingFileLifetime0=0
    transferURL0=gsiftp://lxdpm102.cern.ch/lxdpm102.cern.ch:/data02/dteam/2007-09-18/20070918-133357-22179-0.txt.305299.0
    SURL1=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt returnStatus.statusCode1=SRM_SPACE_AVAILABLE fileSize1=0
    remainingPinLifetime1=419 remainingFileLifetime1=0
    transferURL1=gsiftp://lxdpm102.cern.ch/lxdpm102.cern.ch:/data02/dteam/2007-09-18/20070918-133357-22179-1.txt.305299.1 returnStatus.statusCode=SRM_SUCCESS
    
    Files transfered
     
    srmPutDone srm://lxdpm102.cern.ch:8446
    requestToken=a1a0c403-305a-44b9-99d4-55ba5c9d4101
    SURL["$SPLIT{srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt
    srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt}" ]
    It returns:
    surl0=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt returnStatus.statusCode0=SRM_SUCCESS
    surl1=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt returnStatus.statusCode1=SRM_SUCCESS
    returnStatus.statusCode=SRM_SUCCESS
    
    srmPrepareToGet srm://lxdpm102.cern.ch:8446
    fileRequests.SURL[srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt
    srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt]
    desiredFileStorageType=PERMANENT transferProtocols[gsiftp rfio]
    It returns:
    requestToken=2852261d-22d1-437f-b1b3-c30ec3f163e8
    sourceSURL0=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-0.txt returnStatus.statusCode0=SRM_REQUEST_QUEUED
    sourceSURL1=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt returnStatus.statusCode1=SRM_REQUEST_QUEUED
    returnStatus.statusCode=SRM_REQUEST_QUEUED
     
    srmAbortFiles srm://lxdpm102.cern.ch:8446
    requestToken=2852261d-22d1-437f-b1b3-c30ec3f163e8
    SURL[srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt]
    It returns:
    surl0=srm://lxdpm102.cern.ch:8446/dpm/cern.ch/home/dteam/20070918-133357-22179-1.txt returnStatus.statusCode0=SRM_INVALID_PATH
    returnStatus.explanation="Failed for all SURLs"
    returnStatus.statusCode=SRM_FAILURE
    
  2. An srmLs on a big directory can crash the server. This has been fixed.
  3. srmLs responses from dpm return the list of files even if numOfLevels is 0 This has been fixed.
  4. srmPing should return 2 key-value pairs in the otherInfo structure: backend_type=DPM and backend_version=. This has been FIXED
  5. A garbage collector for expired spaces should be enabled. This has been FIXED
  6. srmExtendFileLifeTime called without request token crashes the server. This has been FIXED
  7. srmPrepareToPut on the same SURL returned SRM_INVALID_REQUEST instead of SRM_DUPLICATION_ERROR at the file level. This has been FIXED
  8. srmPrepareToPut on the same SURL with overwrite flag on succeeds instead of returning SRM_FILE_BUSY at file level. This has been FIXED
  9. srmPrepareToPut on the same SURL with overwrite flag on aborts the previous request and allows the second to succeed. The specs have been relaxed to accept this behavior
  10. Moving a file SURL in a new directory fails. This has been FIXED
  11. srmExtendFileLifeTime on TURL expired returns SRM_SUCCESS. This has been FIXED
  12. srmExtendFileLifeTime on TURL succeeded after a put cycle. This has been FIXED
  13. srmLs with FullDetails=TRUE and NumOfLevels=0 on a (set of) SURL file(s) does not return file locality mandatory output parameter. This has been FIXED
  14. Is srmCopy implemented ? The request remains in status SRM_REQUEST_INPROGRESS for long time (more than 9 minutes) This has been FIXED srmCopy is not implemented and returns SRM_NOT_SUPPORTED as foreseen by the spec.
  15. FullDetail on srmLs not supported since LifetimeLeft not reported. (non relevant according to WLCG MoU ) This has been FIXED

CASTOR CERN (as of October 5nd, 2007)

  1. An srmPrepareToPut with non-supported protocol returns SRM_INVALID_REQUEST instead of SRM_NOT_SUPPORTED : - URGENT
    
    srmPrepareToPut srm://lxb6033.cern.ch:8443 fileRequests.SURL[srm://lxb6033.cern.ch:8443/castor/cern.ch/grid/dteam/20071005-100932-20080-0.txt] fileRequests.expectedFileSize[2713] desiredPinLifeTime=600 desiredFileStorageType=PERMANENT transferProtocols[pippo]
    It returns:
    returnStatus.explanation="Protocol not supported" returnStatus.statusCode=SRM_INVALID_REQUEST
    
  2. srmStatusOfPutRequest changes status over time in the following:
    srmPrepareToPut srm://lxb6033.cern.ch:8443 fileRequests.SURL[srm://lxb6033.cern.ch:8443/castor/cern.ch/grid/dteam/20071005-100932-20080-0.txt] fileRequests.expectedFileSize[2713] desiredPinLifeTime=600 desiredFileStorageType=PERMANENT transferProtocols[pippo] 
    It returns:
    returnStatus.explanation="Protocol not supported" returnStatus.statusCode=SRM_INVALID_REQUEST
    
    The PrepareToPut does not return a request ID and therefore the following:
    
    srmStatusOfPutRequest srm://lxb6033.cern.ch:8443 requestToken=${putRequestToken} SURL[srm://lxb6033.cern.ch:8443/castor/cern.ch/grid/dteam/20071005-100932-20080-0.txt] 
    It returns:
    returnStatus.explanation="Request token does not exist" returnStatus.statusCode=SRM_FAILURE
    
  3. SRM_FAILURE returned at file level instead of SRM_AUTHORIZATION_ERROR in srmPrepareToPut This has been FIXED
  4. SRM requests invoked using fully qualified SURLs, return not fully qualified SURLs :
    srmStatusOfPutRequest https://srm-v2.cr.cnaf.infn.it:8443/srm/managerv2 requestToken=138443 SURL[srm://srm-v2.cr.cnaf.infn.it:8443/srm/managerv2?SFN=/castor/cnaf.infn.it/grid/lcg/dteam/test/srm2/20070914-071425-22971-1.txt srm://srm-v2.cr.cnaf.infn.it:8443/srm/managerv2?SFN=/castor/cnaf.infn.it/grid/lcg/dteam/test/srm2/20070914-071425-22971-0.txt] 
    It returns:
    SURL0=srm://srm-v2.cr.cnaf.infn.it:8443/castor/cnaf.infn.it/grid/lcg/dteam/test/srm2/20070914-071425-22971-0.txt returnStatus.explanation0="" returnStatus.statusCode0=SRM_SPACE_AVAILABLE fileSize0=2702 remainingPinLifetime0=86389 remainingFileLifetime0=-1 transferURL0=gsiftp://diskserv-test-2.cr.cnaf.infn.it:2811//castor/cnaf.infn.it/grid/lcg/dteam/test/srm2/20070914-071425-22971-0.txt SURL1=srm://srm-v2.cr.cnaf.infn.it:8443/castor/cnaf.infn.it/grid/lcg/dteam/test/srm2/20070914-071425-22971-1.txt returnStatus.explanation1=" " returnStatus.statusCode1=SRM_DUPLICATION_ERROR returnStatus.explanation="" returnStatus.statusCode=SRM_PARTIAL_SUCCESS
    
    Please note that in input the SURL have the form of:
    srm://:/srm/managerv2?SFN=//
    but in output they are returned as:
    srm://://
    
    This can confuse clients.
    
  5. A file can be in multiple spaces at a given time This has been FIXED - as far as possible
  6. srmStatusOfGetRequest changing global status over time This has been FIXED
  7. srmMkdir returns SRM_AUTHENTICATION_FAILURE instead of SRM_AUTHORIZATION_FAILURE when a user is not allowed to create a directory. This has been FIXED
  8. Get requests stay in status SRM_REQUEST_INPROGRESS for long time resulting in client timeouts. Details can be found here - This has been FIXED
  9. After a successful srmRelease request on a TURL, the TURL status is still pinned instead of released as you can see from the following sequence. This has been FIXED
  10. The listing of an LHCb directory done with a DTEAM cert produces a SOAP error instead of returning SRM_AUTHORIZATION_ERROR. This has been FIXED
  11. The SRM server ends up in a situation where all SRM requests fail with SRM_INTERNAL_ERROR and explanation "Too many threads". This has been FIXED
  12. srmReleaseFiles returns SRM_INTERNAL_ERROR and an Oracle error if called without specifying a request ID (It should return SRM_NOT_SUPPORTED if the request ID must be provided) - The call is supported This has been FIXED
    srmReleaseFiles srm://lxb6033.cern.ch:8443 SURL[srm://lxb6033.cern.ch:8443/castor/cern.ch/grid/dteam/20070902-011446-28200-0.txt]
    It returns:
    returnStatus.explanation="Error caught in srm::getSelectedPin.
    Database error, Oracle code: 923
    ORA-00923: FROM keyword not found where expected
    " returnStatus.statusCode=SRM_INTERNAL_ERROR
    
  13. A ReserveSpace operation returns SRM_INTERNAL_ERROR: This has been FIXED
    srmReserveSpace srm://lxb6033.cern.ch:8443 retentionPolicy=REPLICA accessLatency=ONLINE desiredSizeOfTotalSpace=1048576 desiredSizeOfGuaranteedSpace=1048576 desiredLifetimeOfReservedSpace=180 transferProtocols[gsiftp rfio] 
    It returns:
    lifetimeOfReservedSpace=180 returnStatus.explanation="Error in fillRep for type 1004
    Database error, Oracle code: 1
    ORA-00001: unique constraint (CASTOR_SRM.SYS_C004072) violated" returnStatus.statusCode=SRM_INTERNAL_ERROR
    
  14. Copy transfers to castor at cnaf failing with error "!putDone without a put" during putDone. This has been FIXED
  15. Copy transfers to castor at cern failing with error "Current user does not own this request!" during statusOfPutRequest. Non-reproduceable
  16. Copy transfers from castor_cern failing with error "Bad address" during statusOfGetRequest. This has been FIXED
  17. The listing of a directory which has, on the srm node, a valid owner but no a valid group makes the daemon crash. This has been FIXED
  18. Random inconsistent failures of Put and Get operations. This has been FIXED
    This request remained INPROGRESS for long time.
    
    srmStatusOfGetRequest srm://srm-v2.cern.ch:8443 requestToken=186019 SURL[srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070525-162607-13060-0.txt]
    It returns:
    sourceSURL0=srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070525-162607-13060-0.txt returnStatus.explanation0="" returnStatus.statusCode0=SRM_REQUEST_INPROGRESS returnStatus.explanation="" returnStatus.statusCode=SRM_REQUEST_QUEUED 
    
    For the following request it looks like somehow the file that was just put got lost:
    
    srmStatusOfGetRequest srm://srm-v2.cern.ch:8443 requestToken=185014 SURL[srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070525-025244-23486-1.txt]
    
    It returns:
    sourceSURL0=srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070525-025244-23486-1.txt returnStatus.explanation0="No such file or directory" returnStatus.statusCode0=SRM_INVALID_PATH returnStatus.explanation="" returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
  19. srmPing should return 2 key-value pairs in the otherInfo structure: backend_type=CASTOR and backend_version=. This has been FIXED
  20. srmStatusOfGetRequest returns SRM_SUCCESS instead of SRM_PARTIAL_SUCCESS when only partially success. This has been FIXED
  21. srmStatusOfGetRequest returns SRM_INVALID_REQUEST at file level status instead of SRM_INVALID_PATH This has been FIXED
  22. Filenames that are 255 characters long are not supported. This has been FIXED but not yet made available.
  23. srmLs with FullDetails=TRUE and NumOfLevels=0 on a (set of) SURL file(s) does not return file locality mandatory output parameter. This has been FIXED
  24. File sizes are not set and returned correctly by Put/Get/Bringonline/Copy operations. This has been FIXED
  25. Getting CGSI errors randomly:
    sSOAP FAULT: SOAP-ENV:Client
    "CGSI-gSOAP: Could not open connection !"
    Detail: connect failed in tcp_connect()
    Error: SOAP-ENV:Client CGSI-gSOAP: Could not open connection ! 
                              connect failed in tcp_connect()
    
    This has been FIXED
  26. Uninitialized numOfWaitingFiles in srmGetRequestSummary, returned values not compliant to WLCG decisions. See item #1 in here This has been FIXED
  27. Calls hunging randomly. Mainly transfer functions (check for instance put request requestToken=16993) This has been FIXED
  28. srmExtendedFileLifeTime on TURL returns the status code below at file level even if the PIN on the TURL is still valid. This has been FIXED
    returnStatus.explanation0=No pins left on this file 
    returnStatus.statusCode0=SRM_FILE_LIFETIME_EXPIRED 
    
  29. Copy fails randomly (no errors returned).
  30. srmReleaseFiles on wrong SURL returns incorrect file and request level status. This has been FIXED
  31. Ls with FullDetail=true not correctly implemented. See items #10-12 of WLCG Workshop decisions This has been FIXED

DRM/BeStMan LBNL (as of August 10th, 2007)

  1. SRM_FILE_IN_CACHE is returned as file status in statusOfGetRequest / statusOfCopyRequest responses. In the srm2.2 specification SRM_FILE_IN_CACHE is not reported as a possible return value for file statuses. This has been FIXED
  2. No tools provided for site administrators to reserve space statically for a VO.
  3. srmGetSpaceMetadata fails with SRM_FAILURE instead of succeeding with SRM_SUCCESS if one of the space tokens specified in the request is expired. This has been FIXED
    srmGetSpaceMetaData https://datagrid.lbl.gov:8443/srm/V2/Server spaceTokens[V.275] 
    
    It returns:
    spaceToken0=V.275 returnStatus.statusCode0=SRM_SPACE_LIFETIME_EXPIRED retentionPolicy0=REPLICA accessLatency0=REPLICA owner0=srmguest totalSize0=1048576 guaranteedSize0=1048576 unusedSize0=1048576 lifetimeAssigned0=60 lifetimeLeft0=0 returnStatus.statusCode=SRM_FAILURE
    
  4. srmCopy fails with all other implementations because of the following error: This has been FIXED
    srmStatusOfCopyRequest https://datagrid.lbl.gov:8443/srm/V2/Server requestToken=srmguest:2634(COPY) sourceSURL[srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-080003-7405-0.txt] targetSURL[srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070515-080003-7405-3.txt] 
    
    It returns:
    sourceSURL0=srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-080003-7405-0.txt targetSURL0=srm://srm-v2.cern.ch:8443/castor/cern.ch/grid/dteam/20070515-080003-7405-3.txt returnStatus.explanation0="remote prepareToPut() sends errorReason:Could not get user information: VOMS credential dteam does not match grid mapping default" returnStatus.statusCode0=SRM_AUTHENTICATION_FAILURE fileSize0=2691 estimatedWaitTime0=-1 returnStatus.statusCode=SRM_FAILURE
    
  5. Permanent files are not allowed to live in volatile space . If this case should be allowed, then the correct return value is SRM_INVALID_REQUEST at request level and SRM_FAILURE at file level.
    srmPrepareToPut https://datagrid.lbl.gov:8443/srm/V2/Server fileRequests.SURL[srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082459-9572-0.txt] fileRequests.expectedFileSize[2691] overwriteOption=ALWAYS desiredFileStorageType=PERMANENT targetSpaceToken=V.348 transferProtocols[gsiftp rfio] 
    It returns:
    SURL0=srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082459-9572-0.txt returnStatus.explanation0="space type and file type mismatch." returnStatus.statusCode0=SRM_FAILURE returnStatus.statusCode=SRM_FAILURE
    
    srmPrepareToPut https://datagrid.lbl.gov:8443/srm/V2/Server fileRequests.SURL[srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070529-082843-10005-0.txt] fileRequests.expectedFileSize[2691] overwriteOption=ALWAYS desiredFileStorageType=PERMANENT targetSpaceToken=V.280 transferProtocols[gsiftp rfio] 
    
    It returns NULL
    
  6. Tokens are case insensitive: This has been FIXED
    srmPrepareToPut https://datagrid.lbl.gov:8443/srm/V2/Server fileRequests.SURL[srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082506-10297-0.txt srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082506-10297-1.txt] fileRequests.expectedFileSize[2691] userRequestDescription=Flavia-20070515-082506 desiredFileStorageType=PERMANENT transferProtocols[gsiftp rfio] 
    It returns:
    requestToken=srmguest:2674(PUT) SURL0=srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082506-10297-0.txt returnStatus.explanation0="A default token is assigned" returnStatus.statusCode0=SRM_REQUEST_QUEUED SURL1=srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082506-10297-1.txt returnStatus.explanation1="A default token is assigned" returnStatus.statusCode1=SRM_REQUEST_QUEUED returnStatus.statusCode=SRM_REQUEST_INPROGRESS
    
    srmGetRequestTokens https://datagrid.lbl.gov:8443/srm/V2/Server userRequestDescription=FLAVIA-20070515-082506 
    It returns:
    requestToken0=srmguest:2674(PUT) createdAtTime0=1179210308 returnStatus.statusCode=SRM_SUCCESS
    
  7. srmLs returns SRM_FAILURE at request level instead of SRM_SUCCESS if the file status is SRM_FILE_BUSY. Since the Ls operation is successful, the correct return code is SMR_SUCCESS. This has been FIXED
    srmLs https://datagrid.lbl.gov:8443/srm/V2/Server SURL[srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082350-4047/20070515-082350-4047-0.txt] fullDetailedList=1
    It returns:
    path0=srm://datagrid.lbl.gov:8443/srm/V2/Server?SFN=/srmguest/20070515-082350-4047/20070515-082350-4047-0.txt returnStatus.explanation0="Not on device yet." returnStatus.statusCode0=SRM_FILE_BUSY createdAtTime0=1179210233 fileStorageType0=PERMANENT retentionPolicy0=CUSTODIAL type0=FILE userID0=srmguest mode0=RWX groupID0=defaultGroup mode0=RX otherPermission0=RX returnStatus.statusCode=SRM_FAILURE
    
  8. srmStatusOfGetRequest returns SRM_SUCCESS instead of SRM_PARTIAL_SUCCESS when only partially success. This has been FIXED
  9. srmStatusOfGetRequest returns SRM_FAILURE at file level status instead of SRM_INVALID_PATH when file does not exist. This has been FIXED
  10. srmPrepareToPut and srmStatusOfPutRequest return SRM_REQUEST_INPROGRESS at request level even when all SURLs in the request have been processed and relative TURLs returned. This has been FIXED
  11. srmLs with FullDetails=TRUE and NumOfLevels=0 on a (set of) SURL file(s) does not return file locality mandatory output parameter. This has been FIXED
  12. File sizes are not set and returned correctly by Put/Get/Bringonline/Copy operations. This has been FIXED
  13. srmReserveSpace called without specifying RetentionPolicyInfo returns with SRM_FAILURE instead of SRM_INVALID_REQUEST This has been FIXED
  14. srmPrepareToPut on the same SURL returned SRM_FAILURE at file and request level instead of returning SRM_DUPLICATION_ERROR at file level. This has been FIXED
  15. srmPrepareToPut on the same SURL with overwrite flag on succeeds instead of returning SRM_FILE_BUSY at file level. This has been FIXED
  16. Lifetime granted > Lifetime requested in srmUpdateSpace This has been fixed (non relevant according to WLCG MoU)

STORM INFN/ICTP (as of October 5th, 2007)

  1. srmStatusOfPutRequest changes status over time in the following:
    srmPrepareToPut https://storm02.cr.cnaf.infn.it:8444/srm/managerv2 fileRequests.SURL[srm://storm02.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20071005-145746-8199-0.txt] fileRequests.expectedFileSize[2713] desiredPinLifeTime=600 desiredFileStorageType=PERMANENT transferProtocols[pippo]
    It returns:
    SURL0=srm://storm02.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20071005-145746-8199-0.txt returnStatus.explanation0="" returnStatus.statusCode0=SRM_REQUEST_QUEUED returnStatus.explanation="None of the supplied protocols is supported" returnStatus.statusCode=SRM_NOT_SUPPORTED
    
    srmStatusOfPutRequest https://storm02.cr.cnaf.infn.it:8444/srm/managerv2 requestToken=${putRequestToken} SURL[srm://storm02.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20071005-145746-8199-0.txt]
    It returns:
    returnStatus.explanation="No request by that token" returnStatus.statusCode=SRM_INVALID_REQUEST 
    
  2. Two put operations with overwrite enabled succeed instead of having one returning SRM_FILE_BUSY This has been FIXED : Please check PutOverwriteTransf S2 usecase test
  3. It is possible to extend the Pin lifetime even after a PutDone This has been FIXED :
    srmPutDone https://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2 requestToken=df97d122-2713-4409-9388-06fcf89b0889 SURL[$SPLIT{srm://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20070913-103527-2295-0.txt}] 
    It returns:
    surl0=srm://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20070913-103527-2295-0.txt returnStatus.explanation0="" returnStatus.statusCode0=SRM_SUCCESS returnStatus.explanation="All file requests are successfully completed" returnStatus.statusCode=SRM_SUCCESS
    
    srmExtendFileLifeTime https://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2 requestToken=df97d122-2713-4409-9388-06fcf89b0889 SURL[srm://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20070913-103527-2295-0.txt] newPinLifeTime=600 
    It returns:
    surl0=srm://storm-fe.cr.cnaf.infn.it:8444/srm/managerv2?SFN=/dteam/20070913-103527-2295-0.txt returnStatus.explanation0="Lifetime extended" returnStatus.statusCode0=SRM_SUCCESS fileLifetime0=-1 pinLifetime0=600 returnStatus.explanation="All file requests are successfully completed" returnStatus.statusCode=SRM_SUCCESS
    
  4. remainingPinTime is not returned in srmStatusOfGetRequest :
    srmStatusOfGetRequest https://ibm139.cnaf.infn.it:8444/srm/managerv2 requestToken=5032f045-e40e-421f-a278-81a96158fd8f SURL[srm://ibm139.cnaf.infn.it:8444/srm/managerv2?SFN=/gin/20070816-122743-6888-0.txt] 
    
    It returns:
    sourceSURL0=srm://ibm139.cnaf.infn.it:8444/srm/managerv2?SFN=/gin/20070816-122743-6888-0.txt fileSize0=2702 returnStatus.explanation0="srmPrepareToGet successfully handled!" returnStatus.statusCode0=SRM_FILE_PINNED estimatedWaitTime0=-1 transferURL0=gsiftp://ibm139.cnaf.infn.it:2811/ext3fs/gin/20070816-122743-6888-0.txt remainingTotalRequestTime=0 returnStatus.explanation="All chunks successfully handled!" returnStatus.statusCode=SRM_SUCCESS
    
  5. When srmExtendFileLifeTime is called without specifying new pin or file lifetimes but specifying a request token, the current pin lifetime for the correspondent TURLs should be returned. STORM returns no lifetimes :
    srmExtendFileLifeTime https://ibm139.cnaf.infn.it:8444/srm/managerv2 
    requestToken=2a61849e-96ef-4370-bdb6-ee49d7d809b1 
    SURL[srm://ibm139.cnaf.infn.it:8444/srm/managerv2?SFN=/gin/20070816-110304-24186-0.txt] 
    
    It returns:
    surl0=srm://ibm139.cnaf.infn.it:8444/srm/managerv2?SFN=/gin/20070816-110304-24186-0.txt 
    returnStatus.explanation0="Lifetime extended" 
    returnStatus.statusCode0=SRM_SUCCESS returnStatus.explanation="All file 
    requests are successfully completed" returnStatus.statusCode=SRM_SUCCESS
    
  6. A full detail list does not return the groupID for a file. This has been FIXED
  7. Copy requests to storm_t1 failed with SRM_DUPLICATION_ERROR during the first putDone request . (Please check here) - URGENT
  8. srmcopy test transfers from StoRM fail some time, due to srmStatusOfCopyRequest responses returning SRM_SUCCESS for request level status and SRM_REQUEST_QUEUED for file level status. - URGENT
  9. No tools provided for site administrators to reserve space statically allocating the same class of space to multiple tokens mapped to the same path
  10. srmPrepareToPut and srmStatusOfPutRequest return SRM_FAILURE at request level instead of returning SRM_SPACE_LIFETIME_EXPIRED when the space specified in the request is expired and the space token is still available. If the space token is unavailable SRM_INVALID_REQUEST should be returned. This has been FIXED
  11. srmPing should return 2 key-value pairs in the otherInfo structure: backend_type=StoRM and backend_version= This has been FIXED
  12. The system makes an implicit srmPutDone if the client does not perform this call before the request expires. This has been FIXED
  13. It is possible to put a new file in expired space This has been FIXED
  14. Permissions and other mandatory parameters not fully returned by srmLs when FullDetails=TRUE This has been FIXED
  15. File locality mandatory output parameter not returned by srmLs when FullDetails=TRUE and NumOfLevels=0 for a (set of) file(s). This has been FIXED
  16. 2 srmPrepareToPut with overwrite flag on return SRM_SPACE_AVAILABLE instead of one of them returning SRM_FILE_BUSY. This has been FIXED
  17. Several methods not implemented and not returning SRM_NOT_SUPPORTED This has been FIXED
  18. Description tokens are case insensitive This has been FIXED
  19. Ls on top directory requires the directory path to end with a "/". This has been FIXED
  20. srmPrepareToGet returns SRM_SUCCESS even if not all files are completed successfully. This has been FIXED
  21. The default for NumOfLevels in srmLs is 0 instead of 1 This has been FIXED
  22. FullDetail in srmLs not supported at directory level since the mandatory return values are not returned. This has been FIXED
  23. Moving a SURL to a directory does not work. The return code is SRM_DUPLICATION_ERROR: destination SURL exists.
  24. Moving a file into itself returns SRM_DUPLICATION_ERROR instead of SRM_SUCCESS (this should be a NOP).
  25. srmStatusOfPutRequest returns SRM_FAILURE or SRM_SUCCESS instead of SRM_PARTIAL_SUCCESS if some files failed and some succeeded deepending on the array of SURLs passed as input. This is not correct. Please, check point 26 in here. This has been FIXED
  26. srmStatusOfGetRequest returns SRM_FAILURE or SRM_SUCCESS instead of SRM_PARTIAL_SUCCESS if some files failed and some succeded depending on the array of SURLs passed as input. This is not correct. Please, check point 26 in here. This has been FIXED
  27. srmReserveSpace does not have the input parameter TRetentionPolicyInfo as mandatory This has been FIXED
  28. After putting 2 files and deleting one of them a second Put request on the same two files returns SRM_DUPLICATION_ERROR on the file deleted. This has been FIXED

-- Flavia Donno - 12 October 2007

Edit | Attach | Watch | Print version | History: r77 < r76 < r75 < r74 < r73 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r77 - 2007-11-28 - FlaviaDonno
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    SRMDev All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback