That's the default behavior of xrdcp now. Useful in many other cases.
I reported a bug.
Lukasz
2011/5/16 Andrew Hanushevsky <[log in to unmask]>:
> Hi Doug,
>
> OK, upon closer inspection; this is a bug. Specifying a valid asize will
> cause this error. So, don't specify asize. Plus when in the world do you
> want to specify an asize of 22 bytes anyway (not that it's material to the
> bug).
>
> Andy
>
> On Sun, 15 May 2011, Doug Benjamin wrote:
>
>> Hi,
>>
>> I am trying to debug a behavior that I am seeing in our cluster on a
>> standalone file server with three partitions.
>>
>> when I try to copy a small file into the machine I see this error:
>> (debugging is on)
>>
>> 110515 19:19:58 001 Xrd: Open: Access to server granted.
>> 110515 19:19:58 001 Xrd: Open: Opening the remote file
>> /atlas/local/benjamin/atl010-testfile?oss.asize=22
>> 110515 19:19:58 001 Xrd: Open: File open in progress.
>> 110515 19:19:58 22101 Xrd: SendGenCommand: Sending command Open
>> 110515 19:19:58 22101 Xrd: ReadPartialAnswer: Reading a XrdClientMessage
>> from the server [atl005.phy.duke.edu:1094]...
>> 110515 19:19:58 22101 Xrd: ReaderThread_loc: Reader Thread starting.
>> [xrootd] Total 0.00 MB |====110515 19:19:58 22101 Xrd: ReadPartialAnswer:
>> Server [atl005.phy.duke.edu:1094] answered [kXR_error] (4003)
>> =======110515 19:19:58 22101 Xrd: CheckErrorStatus: Server
>> [atl005.phy.duke.edu] declared: Unable to create
>> /atlas/local/benjamin/atl010-testfile; invalid suggested allocation
>> size(error code: 3005)
>> 110515 19:19:58 001 Xrd: WriteBuffer: File not opened.
>> Error writing to output server.
>> Last server error 3005 ('Unable to create
>> /atlas/local/benjamin/atl010-testfile; invalid suggested allocation size')
>>
>> 110515 19:19:58 001 Xrd: Close: File not opened.
>> 110515 19:19:58 001 Xrd: Disconnect: LogConnID: 0 destroyed
>>
>> *******************************************************
>>
>> On a test machine I have create three partitions:
>> [root@atl005 ~]# df -h /array*
>> Filesystem Size Used Avail Use% Mounted on
>> /dev/mapper/xrootdvg-lv01
>> 222G 188M 211G 1% /array1
>> /dev/mapper/xrootdvg-lv02
>> 226G 188M 214G 1% /array2
>> /dev/mapper/xrootdvg-lv03
>> 226G 188M 214G 1% /array3
>>
>> - Note all have plenty of space.
>>
>> --------------------------- Here is the configuration file
>> ------------------
>> set head = atlhn02.phy.duke.edu
>> set exportpath = /atlas
>> set domainname = *.phy.duke.edu
>> all.adminpath /var/spool/xrootd/admin
>> all.export $(exportpath)
>> oss.space public /array*
>> xrootd.chksum max 3 adler32 /usr/bin/xrdadler32
>> xrootd.seclib /usr/lib64/libXrdSec.so
>> # this specify that we use the 'unix' authentication module, additional
>> one can be specified.
>> sec.protocol /usr/lib64 unix
>> # this is the authorization file
>> acc.authdb /etc/xrootd/auth_file
>> ofs.authorize
>> ofs.notify closew create mkdir mv rm rmdir trunc | /usr/bin/XrdCnsd -d -D
>> 2 -i 90 -b $(head):1095:$(exportpath)/inventory
>>
>> ------------------------ Here is the authorization file (though I do not
>> see it making any difference)
>>
>> # This means that all the users have read access to the datasets
>> u * /atlas lr
>> # This means that all the users have full access to their private dirs
>> u = /atlas/local/@=/ a
>> # This means that this privileged user can do everything
>> # You need at least one user like that, in order to create the
>> # private dir for each user willing to store his data in the facility
>> u xrootd /atlas a
>>
>> ---------------------------------------------------------------- Here is
>> snippets from the xrootd.log
>>
>> ++++++ Storage system initialization started.
>> =====> all.export /atlas
>> =====> oss.space public /array*
>> Config effective /etc/xrootd/xrootd-standalone.cfg oss configuration:
>> oss.alloc 0 0 0
>> oss.cachescan 600
>> oss.compdetect * oss.fdlimit 32678 65356
>> oss.maxsize 0
>> oss.trace 0
>> oss.xfr 1 deny 10800 keep 1200
>> oss.memfile off max 8413181952
>> oss.space public /array1
>> oss.space public /array3
>> oss.space public /array2
>> oss.defaults r/w nocheck nodread nomig norcreate nopurge nostage
>> xattr
>> oss.path /atlas r/w nocheck nodread nomig norcreate nopurge nostage
>> xattr
>> ------ Storage system initialization completed.
>>
>> 110515 19:00:21 19065 XrootdXeq: benjamin.22101:6@atl010 login as benjamin
>> 110515 19:00:21 19065 ofs_open: benjamin.22101:6@atl010 Unable to create
>> /atlas/local/benjamin/atl010-testfile; invalid suggested allocation size
>> 110515 19:00:21 19065 XrootdXeq: benjamin.22101:6@atl010 disc 0:00:00
>>
>> ---------------------------
>>
>> I am at a lost to try to understand why I am getting the errors invalid
>> suggested allocation size
>>
>>
>> Thanks,
>>
>> Doug
>>
>
