We don't implement the GETFLAGS and SETFLAGS ioctls used for +i. Adding the ioctls is pretty easy, but then we need somewhere to put the flags. Currently we don't store a "flags" attribute on inodes, but maybe we could borrow the high bits of the mode attribute for this if we wanted to implement it? CCing ceph-devel to see if Sage/Greg can offer any more background. John On Wed, Jan 28, 2015 at 1:24 AM, Eric Eastman <eric.eastman@xxxxxxxxxxxxxx> wrote: > Should chattr +i work with cephfs? > > Using ceph v0.91 and a 3.18 kernel on the CephFS client, I tried this: > > # mount | grep ceph > 172.16.30.10:/ on /cephfs/test01 type ceph (name=cephfs,key=client.cephfs) > # echo 1 > /cephfs/test01/test.1 > # ls -l /cephfs/test01/test.1 > -rw-r—r-- 1 root root 2 Jan 27 19:09 /cephfs/test01/test.1 > # chattr +i /cephfs/test01/test.1 > chattr: Inappropriate ioctl for device while reading flags on > /cephfs/test01/test.1 > > I also tried it using the FUSE interface: > > # ceph-fuse -m 172.16.30.10 /cephfs/fuse01/ > ceph-fuse[5326]: starting ceph client > 2015-01-27 19:54:59.002563 7f6f8fbcb7c0 -1 init, newargv = 0x2ec2be0 > newargc=11 > ceph-fuse[5326]: starting fuse > # mount | grep ceph > ceph-fuse on /cephfs/fuse01 type fuse.ceph-fuse > (rw,nosuid,nodev,allow_other,default_permissions) > # echo 1 > /cephfs/fuse01/test02.dat > # chattr +i /cephfs/fuse01/test02.dat > chattr: Invalid argument while reading flags on /cephfs/fuse01/test02.dat > > Eric > > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
