I am interested in this because it would be nice to be able to set
tuning options at the root directory level without modifying the server
side configuration files. I also wonder if this issue would cause
problems for ACLs on the root directory.
-Phil
Murali Vilayannur wrote:
Hey Phil,
Sorry I forgot to get back to you on this..
No I don't think this would work.
It is a kernel module issue that I hadnt tracked down fully..
Do you need this feature?
thanks,
Murali
On 6/27/07, Phil Carns <[EMAIL PROTECTED]> wrote:
Just pinging on this one again- has any one else bumped into this
problem?
-Phil
Phil Carns wrote:
> It looks like pvfs2 does not allow you to set xattrs on the root
> directory. Is this expected?
>
> # checking the mount options:
>
> > mount -t pvfs2
> tcp://localhost:3334/pvfs2-fs on /mnt/pvfs2 type pvfs2 (rw,user_xattr)
>
> # confirming that xattrs can be set on a normal directory:
>
> > setfattr -n user.pvfs2.num_dfiles -v "1" /mnt/pvfs2/dir1
> > getfattr -n user.pvfs2.num_dfiles /mnt/pvfs2/dir1
> getfattr: Removing leading '/' from absolute path names
> # file: mnt/pvfs2/dir1
> user.pvfs2.num_dfiles="1"
>
> # trying to set xattrs on the root directory:
>
> > setfattr -n user.pvfs2.num_dfiles -v "1" /mnt/pvfs2
> setfattr: /mnt/pvfs2: Operation not permitted
> > getfattr -n user.pvfs2.num_dfiles /mnt/pvfs2
> /mnt/pvfs2: user.pvfs2.num_dfiles: No such attribute
>
> All of the above is run as root. I don't think it is anything special
> about the num_dfiles attribute either; it looks like I can't set any
> xattrs on the root directory. It always responds with "Operation not
> permitted".
>
> -Phil
>
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
Pvfs2-developers@beowulf-underground.org
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
