URL:
<http://savannah.cern.ch/bugs/?86858>
Summary: odd behavior with xrd when using rm or rmdir inside
of xrd command
Project: XROOTD
Submitted by: bdouglas
Submitted on: 2011-09-19 07:44
Severity: 3 - Normal
Priority: 5 - Normal
Status: None
Privacy: Public
Assigned to: None
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Fixed by commit(s):
_______________________________________________________
Details:
Hello,
I am seeing the following odd behavior with the xrd command
First I connect to the redirector with the command
xrd titan
I get the response that I expect -
root://titan.physics.umass.edu:1094//>
Now if I determine all of the directories or files that I want to remove. In
this example I am going to remove director
/atlas/common/mc11_valid.113642.Pythia8JetsJ7.recon.log.e789_a124_tid365
using the locateall command -
root://titan.physics.umass.edu:1094//> locateall
/atlas/common/mc11_valid.113642.Pythia8JetsJ7.recon.log.e789_a124_tid365181_00
------------- Location #1
InfoType: kXrdcLocDataServer
CanWrite: true
Location: '172.30.49.21:1094'
------------- Location #2
InfoType: kXrdcLocDataServer
CanWrite: true
Location: '172.30.49.14:1094'
I see this directory on two data servers : titan14 and titan21
Now if I remove the directory:
root://titan.physics.umass.edu:1094//> rmdir
/atlas/common/mc11_valid.113642.Pythia8JetsJ7.recon.log.e789_a124_tid365181_00
I remove it from one data server as I expect. Now here is
the unexpected part - I am left in the data server where the
removal took place.
root://titan14:1094//> dirlist /atlas/common
when I issue the dirlist command I finally come back to connecting to the
redirector.
Is this how xrd really should behave.
This seems like an bug to me.
Doug
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?86858>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
