StoRM returns wrong filesize in PtG (STOR-331)

[STOR-333] Add regression tests Created: 23/Aug/13  Updated: 09/Jan/14  Resolved: 26/Aug/13

Status: Closed
Project: StoRM
Component/s: None
Affects Version/s: None
Fix Version/s: None
Security Level: Public (Visbile by non-authn users.)

Type: Sub-task Priority: Major
Reporter: Andrea Ceccanti Assignee: Enrico Vianello
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

1. Create file larger than 2147483647 bytes
2. PtP + globus-url-copy
3. PtG -p returns correct file size.



 Comments   
Comment by Enrico Vianello [ 26/Aug/13 ]

Test added with this commit.

This test does the following operations:

  • creates a file X with size 2049MB
  • ptp X -p
  • globus-url-copy X
  • pd X
  • ptg X -p
  • check the fileSize returned from ptg: it must be 2148532224

With StoRM FE < 1.8.3:

[vianello@omii006-vm02 storm-testsuite]$ pybot --exclude "to-be-fixed" --test "Prepare to get larger files" --variable backEndHost:omii005-vm03.cnaf.infn.it tests/srm/commands/srmPtG.txt 
==============================================================================
srmPtG                                                                        
==============================================================================
Prepare to get larger files :: Regression test for https://issues.... | FAIL |
'============================================================
Sending PtG request to: omii005-vm03.cnaf.infn.it:8444
Before execute:
Afer execute:
Request Status Code 17
Poll Flag 1
============================================================
Polling request status:
Current status: SRM_REQUEST_QUEUED (Ctrl+c to stop polling)..
Current status: SRM_REQUEST_INPROGRESS (Ctrl+c to stop polling).
============================================================
Request status:
  statusCode="SRM_SUCCESS"(0)
  explanation="All chunks successfully handled!"
============================================================
SRM Response:
  requestToken="18209f1e-3c5c-4034-b7e1-e637e653cc11"
  arrayOfFileStatuses (size=1)
      [0] status: statusCode="SRM_FILE_PINNED"(22)
                  explanation="srmPrepareToGet successfully handled!"
      [0] sourceSURL="srm://omii005-vm03.cnaf.infn.it:8444/srm/managerv2?SFN=/testers.eu-emi.eu/tmp.wEVgQ24194"
      [0] fileSize=0
      [0] transferURL="gsiftp://omii005-vm03.cnaf.infn.it:2811//storage/testers.eu-emi.eu/tmp.wEVgQ24194"
============================================================' does not contain 'fileSize=2148532224'
------------------------------------------------------------------------------
srmPtG                                                                | FAIL |
1 critical test, 0 passed, 1 failed
1 test total, 0 passed, 1 failed
==============================================================================
Output:  /home/vianello/storm-testsuite/output.xml
Log:     /home/vianello/storm-testsuite/log.html
Report:  /home/vianello/storm-testsuite/report.html

With StoRM FE 1.8.3:

[vianello@omii006-vm02 storm-testsuite]$ pybot --exclude "to-be-fixed" --test "Prepare to get larger files" --variable backEndHost:omii005-vm03.cnaf.infn.it tests/srm/commands/srmPtG.txt 
==============================================================================
srmPtG                                                                        
==============================================================================
Prepare to get larger files :: Regression test for https://issues.... | PASS |
------------------------------------------------------------------------------
srmPtG                                                                | PASS |
1 critical test, 1 passed, 0 failed
1 test total, 1 passed, 0 failed
==============================================================================
Output:  /home/vianello/storm-testsuite/output.xml
Log:     /home/vianello/storm-testsuite/log.html
Report:  /home/vianello/storm-testsuite/report.html

The fileSize returned by the srmPtG is correct!

Generated at Wed May 06 15:03:22 CEST 2026 using Jira 11.3.2#11030003-sha1:bd741f0b02a315de9bddd49d71ae8ffde8b13b6c.