 |
 |
Hello Andrew, Thank you for your swift response. It's nice to clearly know why the writing didn't work. In my particular case, the origin does support writes. However, since I'm working on a test environment and I'm just getting familiar with the Proxy service, it's too early to say whether cache pass-through functionality will be desired. I like your solution with the different proxies and will try it out in the next steps. Best Regards, Mihai -----Original Message----- From: Andrew Hanushevsky [mailto:[log in to unmask]] Sent: 01 March 2018 18:10 To: Fabrizio Furano <[log in to unmask]> Cc: [log in to unmask]; Mihai Patrascoiu <[log in to unmask]>; Matevz Tadel <[log in to unmask]> Subject: Re: Testing the XrdPss with cachelib - Issues with writing Correct, we don't support a writable cache because that's not what a cache is all about. Does the origin support writes? If so, we could potentially provide a cache passthrough option. Otherwise, if the readable and writable path differ, he could have run two proxies -- one caching for read access and a passthru proxy for writing then setup a redirect directive in the primary proxy (i.e. the one that will be initially used) to direct writes to the passthru proxy based on path. Andy On Thu, 1 Mar 2018, Fabrizio Furano wrote: > Hi, > > Mihai is trying to setup a small Pss machine that also works as a cache. > > For reading it seems to work fine, yet it stubbornly refuses to write > files with this error: > >> 180301 17:27:38 13788 XrdFileCache_Manager: debug Cache::Attach() >> root:[log in to unmask]:1094//eos/xdc/testing/hello.txt?&oss.a >> size=14&oss.lcl=1 location: <deferred open> >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 ofs_fstat: >> fn=/eos/xdc/testing/hello.txt >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdResponse: 0100 >> sending 46 data bytes; status=0 >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdProtocol: 0100 >> req=write dlen=14 >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdProtocol: 0100 >> fh=0 write 14@0 >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 ofs_write: 14@0 >> fn=/eos/xdc/testing/hello.txt >> 180301 17:27:38 13788 ofs_write: root.3008:20@xdc-test-fst1 Unable to >> write /eos/xdc/testing/hello.txt; operation not supported >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdProtocol: 0100 >> discarding 0 bytes >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdResponse: 0100 >> sending err 3005: Unable to write /eos/xdc/testing/hello.txt; >> operation not supported >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 XrootdProtocol: 0100 >> req=close dlen=0 >> 180301 17:27:38 13788 root.3008:20@xdc-test-fst1 ofs_close: use=1 >> fn=/eos/xdc/testing/hello.txt > > If we remove the directive pss.cachelib then writes work instead. > > Can anyone give us a clue please ? > > Thank you > Fabrizio and Mihai > > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1