-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot create directory #151
Comments
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, On Oct 22, 2014, at 2:55 AM, marcelkuri notifications@github.com wrote:
|
Hi, Wei Yang. Marcel |
Hi Marcel, Xrootd storage following its own ACL rules and “root” is treated as an ordinary users… Does the xrootd daemon has write permission to /data/files/data/xrootdfs on all data servers? regards, On Oct 22, 2014, at 10:06 AM, marcelkuri notifications@github.com wrote:
|
Hi, Wei. Now, all users with xrootd group can create a folder under /atlas. Thank you very much, Wei Marcel |
Hi Marcel, Good to know that it works. Remind you that you will still have the problem I described until you get xrootd release 4.0.4. Also, tough this problem will be fixed in xrootd 4.0.4 (which is already available as RPM), it is still packaged as xrootd4-4.0.4 rpms. I was told that we will go back to xrootd rpms (as opposed to xrootd4 rpms) in release 4.1, which is supposed to come out by the end of this month. regards, On Oct 22, 2014, at 1:57 PM, marcelkuri notifications@github.com wrote:
|
With the xrootd release 4.0.4 I cannot mount /atlas. |
I believe this has been resolved. Please reopen if that is not the case. |
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
where:
496 is the xrootd uid number
492 is the xrootd gid number
"/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
Thanks
Marcel
The text was updated successfully, but these errors were encountered: