2024-11-10T11:44:21.780Z

<Gregory Orange> Since it's being discussed: If I am reading the process correctly, since Squid 19.2.0 has been released, the next 17.2.x (i.e. 17.2.8) release will be the last for Quincy. Is that right? Therefore Quincy would then officially be EOL. Is that right?

2024-11-10T17:47:43.421Z

<Markuze> I'm getting this error in a loop when compiling latest ceph and running vstart:
```/home/alex/ceph/build/bin/ceph -c /home/alex/ceph/build/ceph.conf -k /home/alex/ceph/build/keyring fs volume ls 
no valid command found; 10 closest matches:
fs authorize <filesystem> <entity> <caps>...
fs dump [<epoch:int>]
fs compat show <fs_name>
fs new <fs_name> <metadata> <data> [--force] [--allow-dangerous-metadata-overlay] [<fscid:int>] [--recover] [--yes-i-really-really-mean-it] [<set>...]
fs fail <fs_name> [--yes-i-really-mean-it]
fs rm <fs_name> [--yes-i-really-mean-it]
fs reset <fs_name> [--yes-i-really-mean-it]
fs ls
fs get <fs_name>
fs set <fs_name> <var:max_mds|allow_dirfrags|allow_new_snaps|allow_standby_replay|bal_rank_mask|balance_automate|balancer|cluster_down|down|inline_data|joinable|max_file_size|max_xattr_size|min_compat_client|refuse_client_session|refuse_standby_for_another_fs|session_autoclose|session_timeout|standby_count_wanted> <val> [--yes-i-really-mean-it] [--yes-i-really-really-mean-it]```

2024-11-10T20:08:43.605Z

<Markuze> for some reason  `fs volume ls` is not recognized and vstart breaks.

2024-11-10T23:20:09.943Z

<gregsfortytwo> This usually means either the whole manager, or the volumes module, aren’t running