On 24/02/2015 09:20, Xavier Villaneau wrote:
[root@z-srv-m-cph01 ceph]# ceph mds stat
e1: 0/0/0 up
1. question: why the MDS are not stopped?
This is just confusing formatting. 0/0/0 means 0 up, 0 in, max_mds=0.
This status indicates that you have no filesystem at all.
2. When I try to remove them:
# ceph mds rm mds.z-srv-m-cph01 z-srv-m-cph01
Invalid command: mds.z-srv-m-cph01 doesn't represent an int
mds rm <int[0-]> <name (type.id)> : remove nonactive mds
Error EINVAL: invalid command
In the mds rm command, the <int[0-]> refers to the ID of the metadata
pool used by CephFS (since there can only be one right now). And the
<name (type.id)> is simply mds.n where n is 0, 1, etc. Maybe there are
other possible values for type.id, but it worked for me.
This does not refer to the metadata pool ID. It's an MDS "gid", which
is the unique ID assigned to a running daemon (changes if you restart
the daemon). You can only "rm" an MDS if it is not currently holding an
MDS rank.
When you do "ceph mds dump", if there are any up daemons, you can see
them at the end of the output like this:
4113: 172.16.79.251:6818/46415 'a' mds.0.1 up:active seq 2
The <name (type.id)> part is a red herring, it's in the syntax
definition of the command but not actually used (presumably historical,
possibly just a bug). Leave it out.
Anyway, "mds rm" doesn't have anything to do with actually stopping a
daemon, which is an operation purely local to the host it's running on.
You'd only want to do "mds rm" as a cleaning-up task afterwards to
remove any ghost of that daemon that was lingering in the MDS map.
I don't know anything about the ansible scripts you're using, so can't
say much more than that about what you should expect them to be doing in
this situation.
Cheers,
John
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
