Hi Marcel,
Your previous question indicate that you are running xrootd release 4.0.0. There is a known bug in xrootd release 4.0.0 - 4.0.3 that prevent mkdir from working in certain cases. For example, assuming /atlas exists on all your data servers, you should be able to create /atlas/dir1 without issue, but _may_ run into this exact error message if you try to create /atlas/dir1/dir2 (unless /atlas/dir1 exists on all data servers).
If this fit your scenario, then please wait for the next xrootd release. We tagged xrootd 4.0.4 today and rpm will likely come out very soon (but will be named xrootd-4.0.4…, not be named xrootd4-4.0.4… per request from the EPEL repo maintainer).
regards,
Wei Yang | [log in to unmask] | 650-926-3338(O)
On Oct 22, 2014, at 2:55 AM, marcelkuri <[log in to unmask]> wrote:
> I create a automount file with this content:
> /atlas -fstype=fuse,rw,uid=496,gid=492,allow_other,rdr=root://lipnode01:1094//data/xrootdfs :xrootdfs.sh
>
> "/atlas" is mounted correctly, I can list the files and even create a new file under /atlas.
> But when I try to create a directory I get this error:
>
> $ mkdir teste2
> mkdir: cannot create directory `teste2': No such file or directory
>
> —
> Reply to this email directly or view it on GitHub.
>
—
Reply to this email directly or view it on GitHub.
{"@context":"http://schema.org","@type":"EmailMessage","description":"View this Issue on GitHub","action":{"@type":"ViewAction","url":"https://github.com/xrootd/xrootd/issues/151#issuecomment-60115433","name":"View Issue"}}
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
