Hi, if you don't specifically assign an MDS to a CephFS, the standby daemons will be standby in general, so for all Filesystems. You can configure a FS affinity though [0]:

You may set mds_join_fs on the standby to enforce your preference:

$ ceph config set mds.b mds_join_fs cephfs

So in your case, you set it like this: $ ceph config set mds.MONERO.podster3.gwtegj mds_join_fs MONERO Regarding the size you might need to provide more details, not sure what exactly you're referring to from your output. Regards, Eugen [0] https://docs.ceph.com/en/latest/cephfs/standby/#configuring-mds-file-system-... Zitat von lejeczek via ceph-users <ceph-users@ceph.io>:

Hi guys.

Is this ok & expected that standby MDS for a filesystem looks as such:

-> $ ceph fs status APKI APKI - 4 clients ==== RANK  STATE           MDS              ACTIVITY     DNS    INOS  DIRS   CAPS  0    active  APKI.podster2.gsniot  Reqs:    0 /s  8505   5516 143   2757       POOL          TYPE     USED  AVAIL cephfs.APKI.meta  metadata   671M  74.0G cephfs.APKI.data    data    16.1G  74.0G      STANDBY MDS  APKI.podster3.utwwpp MONERO.podster3.gwtegj MDS version: ceph version 20.1.1 (dd9c546413d50a90668289255a256022ea21f0c0) tentacle (rc - RelWithDebInfo)

What puzzles me from that above is: MONERO.podster3.gwtegj I have only two files systems - this is a small lab with ceph - and both were created with "default" ceph cmd, meaning that pools where created automatically by cmd. Is there no special and exclusive relationship between file system & MDS - MONERO.podster3 was created when file system/volume MONERO was created, yet it is available to a different file system?

(what also boggles my mind is "size" the two file systems report, like they share something, but not relevant yet in case I have something seriously dis-configured relating what stat "status" showed)

many thanks, L. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io