Hi, I'm working on a small POC for a ceph setup on 4 old C6100 power-edge. I had to install Octopus since latest versions were unable to detect the HDD (too old hardware ??).  No matter, this is only for training and understanding Ceph environment. My installation is based on https://download.ceph.com/rpm-15.2.12/el8/noarch/cephadm-15.2.12-0.el8.noar… bootstrapped. I'm reaching the point to automate the snapshots (I can create snapshot by hand without any problem). The documentation https://download.ceph.com/rpm-15.2.12/el8/noarch/cephadm-15.2.12-0.el8.noar… says to use the snap_schedule module but this module does not exist. # ceph mgr module ls | jq -r '.enabled_modules []' cephadm dashboard iostat prometheus restful Have I missed something ? Is there some additional install steps to do for this module ? Thanks for your help. Patrick _______________________________________________ ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an email to ceph-users-leave(a)ceph.io

Hi, still some problems with snap_schedule as as the ceph fs snap-schedule namespace is not available on my nodes. [ceph: root@mostha1 /]# ceph mgr module ls | jq -r '.enabled_modules []' cephadm dashboard iostat prometheus restful snap_schedule [ceph: root@mostha1 /]# ceph fs snap_schedule no valid command found; 10 closest matches: fs status [<fs>] fs volume ls fs volume create <name> [<placement>] fs volume rm <vol_name> [<yes-i-really-mean-it>] fs subvolumegroup ls <vol_name> fs subvolumegroup create <vol_name> <group_name> [<pool_layout>] [<uid:int>] [<gid:int>] [<mode>] fs subvolumegroup rm <vol_name> <group_name> [--force] fs subvolume ls <vol_name> [<group_name>] fs subvolume create <vol_name> <sub_name> [<size:int>] [<group_name>] [<pool_layout>] [<uid:int>] [<gid:int>] [<mode>] [--namespace-isolated] fs subvolume rm <vol_name> <sub_name> [<group_name>] [--force] [--retain-snapshots] Error EINVAL: invalid command I think I need your help to go further 😕 Patrick Le 19/09/2023 à 10:23, Patrick Begou a écrit : _______________________________________________ ceph-users mailing list -- ceph-users(a)ceph.io To unsubscribe send an email to ceph-users-leave(a)ceph.io

Hi Patrick, sorry for the bad copy/paste. As it was not working I have also tried with the module name 😕 [ceph: root@mostha1 /]# ceph fs snap-schedule no valid command found; 10 closest matches: fs status [<fs>] fs volume ls fs volume create <name> [<placement>] fs volume rm <vol_name> [<yes-i-really-mean-it>] fs subvolumegroup ls <vol_name> fs subvolumegroup create <vol_name> <group_name> [<pool_layout>] [<uid:int>] [<gid:int>] [<mode>] fs subvolumegroup rm <vol_name> <group_name> [--force] fs subvolume ls <vol_name> [<group_name>] fs subvolume create <vol_name> <sub_name> [<size:int>] [<group_name>] [<pool_layout>] [<uid:int>] [<gid:int>] [<mode>] [--namespace-isolated] fs subvolume rm <vol_name> <sub_name> [<group_name>] [--force] [--retain-snapshots] Error EINVAL: invalid command I'm reading the same documentation, but for Octopus: https://docs.ceph.com/en/octopus/cephfs/snap-schedule/# I think that if "ceph mgr module enable snap_schedule" was not working without the "--force" option, it was because something was wrong in my Ceph install. Patrick Le 19/09/2023 à 14:29, Patrick Donnelly a écrit : > https://docs.ceph.com/en/quincy/cephfs/snap-schedule/#usage > > ceph fs snap-schedule > > (note the hyphen!) > > On Tue, Sep 19, 2023 at 8:23 AM Patrick Begou > &lt;Patrick.Begou(a)univ-grenoble-alpes.fr&gt; wrote: >> Hi, >> >> still some problems with snap_schedule as as the ceph fs snap-schedule >> namespace is not available on my nodes. >> >> [ceph: root@mostha1 /]# ceph mgr module ls | jq -r '.enabled_modules []' >> cephadm >> dashboard >> iostat >> prometheus >> restful >> snap_schedule >> >> [ceph: root@mostha1 /]# ceph fs snap_schedule >> no valid command found; 10 closest matches: >> fs status [<fs>] >> fs volume ls >> fs volume create <name> [<placement>] >> fs volume rm <vol_name> [<yes-i-really-mean-it>] >> fs subvolumegroup ls <vol_name> >> fs subvolumegroup create <vol_name> <group_name> [<pool_layout>] >> [<uid:int>] [<gid:int>] [<mode>] >> fs subvolumegroup rm <vol_name> <group_name> [--force] >> fs subvolume ls <vol_name> [<group_name>] >> fs subvolume create <vol_name> <sub_name> [<size:int>] [<group_name>] >> [<pool_layout>] [<uid:int>] [<gid:int>] [<mode>] [--namespace-isolated] >> fs subvolume rm <vol_name> <sub_name> [<group_name>] [--force] >> [--retain-snapshots] >> Error EINVAL: invalid command >> >> I think I need your help to go further 😕 >> >> Patrick >> Le 19/09/2023 à 10:23, Patrick Begou a écrit : >>> Hi, >>> >>> bad question, sorry. >>> I've just run >>> >>> ceph mgr module enable snap_schedule --force >>> >>> to solve this problem. I was just afraid to use "--force" 😕 but as I >>> can break this test configuration.... >>> >>> Patrick >>> >>> Le 19/09/2023 à 09:47, Patrick Begou a écrit : >>>> Hi, >>>> >>>> I'm working on a small POC for a ceph setup on 4 old C6100 >>>> power-edge. I had to install Octopus since latest versions were >>>> unable to detect the HDD (too old hardware ??). No matter, this is >>>> only for training and understanding Ceph environment. >>>> >>>> My installation is based on >>>> https://download.ceph.com/rpm-15.2.12/el8/noarch/cephadm-15.2.12-0.el8.noar… >>>> bootstrapped. >>>> >>>> I'm reaching the point to automate the snapshots (I can create >>>> snapshot by hand without any problem). The documentation >>>> https://download.ceph.com/rpm-15.2.12/el8/noarch/cephadm-15.2.12-0.el8.noar… >>>> says to use the snap_schedule module but this module does not exist. >>>> >>>> # ceph mgr module ls | jq -r '.enabled_modules []' >>>> cephadm >>>> dashboard >>>> iostat >>>> prometheus >>>> restful >>>> >>>> Have I missed something ? Is there some additional install steps to >>>> do for this module ? >>>> >>>> Thanks for your help. >>>> >>>> Patrick >>>> _______________________________________________ >>>> ceph-users mailing list -- ceph-users(a)ceph.io >>>> To unsubscribe send an email to ceph-users-leave(a)ceph.io >>> _______________________________________________ >>> ceph-users mailing list -- ceph-users(a)ceph.io >>> To unsubscribe send an email to ceph-users-leave(a)ceph.io >> _______________________________________________ >> ceph-users mailing list -- ceph-users(a)ceph.io >> To unsubscribe send an email to ceph-users-leave(a)ceph.io >

Hi Patrick, I agree that learning Ceph today with Octopus is not a good idea, but, as a newbie with this tool, I was not able to solve the HDD detection problem and my post about it on this forum do not provide any help (https://lists.ceph.io/hyperkitty/list/ceph-users@ceph.io/message/OPMWHJ4ZFC…). I've also looked for a list of new unsupported hardware  between Octopus and Pacific without success. I've also received a private mail from a Sweden user reading the forum last week and having the same HDD detection problem with 17.2.6. He was asking if I have solved it. He tells me he will try to debug. In my mind, an old version of Ceph on an old material had more chances to be stable and bug free too. Yes I have created file systems (datacfs) and I can create a snapshot by hand using cephadm. I've just tested: # ceph fs set datacfs allow_new_snaps true # ceph-fuse /mnt # mkdir /mnt/.snap/$(TZ=CET date +%Y-%m-%d:%H-%M-%S) and I have a snapshot. I can remove it too. May be today my goal should be: 1- try to undo   "ceph mgr module enable snap_schedule --force" (always a bad idea in my mind to use options like "--force") 2- launch update to nautilus now that all HDDs are configured. In my Ceph learning process there is also the step to test update procedures.