Documentation #16587
closed
"ceph mds getmap" command does not exit gracefully
Added by Rohith Radhakrishnan almost 8 years ago.
Updated over 7 years ago.
Description
After ceph mds getmap command is executed "xtermxtermxtermxtermxtermxterm" is printed onscreen.This should be removed. Sample output below.
ceph mds getmap
got fsmap epoch 5
▒~
▒i▒e v0.20client writeable rangesdefault file layouts on dirsdir inode in separate objectds uses versioned encodingdirfrag is stored in omafile layout v2▒▒▒<,h▒▒h▒mds1
▒*▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
~
base v0.20client writeable rangesdefault file layouts on dirsdir inode in separate objectds uses versioned encodingdirfrag is stored in omafile layout v2y▒{W'ʱy▒{Wsʱh▒cephfsh▒xtermxtermxtermxtermxtermxtermems@rack2-client-3:/var/log/sandisk/IFOS-1.4.0.19/latest$ xtermxtermxtermxtermxtermxterm
ceph mds getmap is something like "ceph osd getmap", it get the mdsmap in binary version, not for human-readable. So you would like to do " ceph mds getmap > mymdsmap "
Is it not worth having it in a human readable format? or atleast have a warning or a separate section for the "getmaps" command, having binary format, in general. Right now it is part of general ceph commands. So users wouldn't be expecting this e.g below:-
CEPH – CEPH ADMINISTRATION TOOL
ceph mds [ add_data_pool | cluster_down | cluster_up | compat | deactivate | dump | fail | getmap | newfs | remove_data_pool | rm | rmfailed | set | set_max_mds | set_state | stat | stop | tell ] ...
ceph mon [ add | dump | getmap | remove | stat ] ...
- Tracker changed from Bug to Documentation
ceph mds dump will give you human-readable version. Similar logical for "cpeh osd dump " and "ceph osd getmap"
Maybe a bit lack of documentation saying the output is binary. would you like to fix it ?
It would be good to differentiate the commands which give binary output from the normal commands. Yeah, a bit of documentation in help would be sufficient for all the getmap commands in general.
- Status changed from New to Closed
mds getmap is deprecated in the latest code, so I don't think we'll be doing any new documentation of it.
Also available in: Atom
PDF