Hi,
So ... Andy helped me solve the thing off the list. I had a typo in the config
file and a bug in my head, not taking into account that export specifies
prefixes and not directories so my /tas and /tas-N entries got mixed up.
All works perfect now :)
Cheers,
Matevz
On 08/29/11 17:36, Matevz Tadel wrote:
> I tried most of the things I could think of by now :)
>
> This is the (current) config file:
>
> if nfs-3.t2.ucsd.edu
> all.export /tas-3 global writable
> else if nfs-5.t2.ucsd.edu
> all.export /tas-4 global writable
> all.export /tas-5 global writable
> else if nfs-6.t2.ucsd.edu
> all.export /tas-6 global writable
> all.export /tas global writable
> else if nfs-7.t2.ucsd.edu
> all.export /tas-7 global writable
> all.export /tas global writable
> else if uaf-*.t2.ucsd.edu
> all.export /store global readonly
> else if xrootd.t2.ucsd.edu
> all.export /store global readonly
> all.export /tas-3 local writable
> all.export /tas-4 local writable
> all.export /tas-5 local writable
> all.export /tas-6 local writable
> all.export /tas-7 local writable
> all.export /tas local writable
> else
> all.export /tmp local readonly
> fi
>
> And the problem is that write requests to root://xrootd.t2.ucsd.edu//tas-3/ get
> redirected to all the nodes, not only to nfs-3 which actually holds the partition.
>
> Is there any hope to get this "right" (the way I want it)?
>
> I found this in the cmsd config manual: "During the subscription process, each
> server indicates the file paths to which it is willing to provide data access."
> so i still have some hope.
>
> Cheers,
> Matevz
>
> On 08/25/11 20:27, Matevz Tadel wrote:
>> Hi,
>>
>> At UCSD we have a set of read-only servers (uaf-X, hadoop, all serving /store namespace) and now I'm adding another set of read-write servers (nfs-X, local disk, each serving /tas-X top directory).
>>
>> All these guys report to a common manager, xrootd.t2.ucsd.edu.
>>
>> Now, writing works if I write directly to the new machines, like:
>> xrdcp some-file root://nfs-3.t2.ucsd.edu//tas-3/xrd-write-test/foo
>> but (mostly) fails when I try writing through the redirector:
>> xrdcp some-file root://xrootd.t2.ucsd.edu//tas-3/xrd-write-test/foo
>>
>> Looking at logs, I see the write request is forwarded to a random node. It works if this is nfs-3 but fails with:
>> Last server error 3010 ('Unable to create /tas-3/xrd-write-test/jebo.zotarccxx; Permission denied')
>> if it's one of uaf-X machines. Also, this pollutes the name-space (that is, a subsequent write attempt with the same file name will fail immediately with this error from the redirector itself:
>> Last server error 3011 ('Unable to create new file; file already exists.')
>>
>> What do I have to add into configuration, for each set of machines, to specify what part of namespace they are serving?
>> Something like this?
>> all.export /store if uaf-*.t2.ucsd.edu
>> all.export /nfs-3 if nfs-3.t2.ucsd.edu
>>
>> Will this also work for writing?
>>
>> Cheers,
>> Matevz
>
