On Sun, Aug 22, 2021 at 2:25 AM David Prude <david@xxxxxxxxxxxxxxxx> wrote: > > Patrick, > > Thank you so much for writing back. > > > Did you set the new "subvolume" flag on your root directory? The > > probable location for EPERM is here: > > > > https://github.com/ceph/ceph/blob/d4352939e387af20531f6bfbab2176dd91916067/src/mds/Server.cc#L10301 > > > > You can unset it using: > > > > setfattr -n ceph.dir.subvolume -v 0 /path/to/cephfs/root > > This seems to have resolved the issue! > > root@ceph-01:~# cd /mnt/dncephfs/ > root@ceph-01:/mnt/dncephfs# setfattr -n ceph.dir.subvolume -v 0 . > root@ceph-01:/mnt/dncephfs# cd samba/dnstor-test/.snap > root@ceph-01:/mnt/dncephfs/samba/dnstor-test/.snap# mkdir testsnapshot > > What is a bit perplexing here is that we certainly did not set that > attribute manually. Are there ceph command sequences that could have > enabled that flag as a side-effect? Since I cannot thing of anything I > did that would have enabled this I am a bit concerned that I might > re-enable this without my knowledge in the future. It's possible a bug in the "fs subvolume" interface did it but we've not heard any other reports of this problem. Otherwise, nothing else in Ceph internally uses it. -- Patrick Donnelly, Ph.D. He / Him / His Principal Software Engineer Red Hat Sunnyvale, CA GPG: 19F28A586F808C2402351B93C3301A3E258DD79D _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |