Re: snap-schedule not running

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Have you checked debug logs yet? I found the reason for my failing snapshots in the debug logs. Be aware that they can quickly fill up your filesystem, but since it's easily reproducible, you don't the debug level for too long.

Zitat von Sophonet <ceph@xxxxxxxxxxxxxxxxxx>:

Hi Eugen,
 
thanks for the info - yes, allow_new_snaps is set.

The schedule is set for a subfolder of a cephfs. Interestingly, I can successfully create snapshots (or the schedule for them) in /.snap (the snapshot folder of the root folder in the filesystem), but not in any existing or newly created (sub-)subfolder /subfolder/.snap - error is "Operation not permitted.".

This only happens to one particular cephfs. Other filesystem do not show this problem and (scheduled) snapshots can be created everywhere. File permissions are identical to the problematic one as well as client auth caps.

Any idea anyone? Of course I could set up the problematic filesystem from scratch again, but I rather would like to understand the cause of the problem.

Thanks,

Sophonet
 
"Eugen Block" eblock@xxxxxx – 1. September 2025 09:26
Hi,
 
this reminds me of my own experiment [0]. Did you enable new snapshots [1]?
 
$ ceph fs set <fs_name> allow_new_snaps true
 
Regards,
Eugen
 
[0] https://tracker.ceph.com/issues/67790#note-4
[1] https://docs.ceph.com/en/reef/dev/cephfs-snapshots/#creating-a-snapshot
 
Zitat von Sophonet <ceph@xxxxxxxxxxxxxxxxxx>:
 
> Quick update / follow-up question:
>
> In the mgr logs I have seen that the schedule is indeed running, but 
> snapshots cannot be created due to an error when 
> cephfs.LibCephFS.mkdir ist called (Operation not permitted). 
> Apparently, the scheduler is not using client.admin as ID (for the 
> keyring when connecting to the target filesystem), since "ceph auth 
> get client.admin" shows "caps mds = allow *".
>
> I have not found any documentation about setting the http://client.ID for a 
> schedule. Any hints how the permission error can be avoided?
>
> Thanks,
>
> sophonet
>
> (I am posting this update for the third time now, hoping that the 
> two earlier attempts that did not show up in the list are not just 
> delayed...)
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx
 
 
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
 

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx


_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux