]> git.proxmox.com Git - ceph.git/blame - ceph/doc/cephfs/administration.rst
update sources to v12.1.2
[ceph.git] / ceph / doc / cephfs / administration.rst
CommitLineData
7c673cae
FG
1
2CephFS Administrative commands
3==============================
4
5Filesystems
6-----------
7
8These commands operate on the CephFS filesystems in your Ceph cluster.
9Note that by default only one filesystem is permitted: to enable
10creation of multiple filesystems use ``ceph fs flag set enable_multiple true``.
11
12::
13
14 fs new <filesystem name> <metadata pool name> <data pool name>
15
16::
17
18 fs ls
19
20::
21
22 fs rm <filesystem name> [--yes-i-really-mean-it]
23
24::
25
26 fs reset <filesystem name>
27
28::
29
30 fs get <filesystem name>
31
32::
33
34 fs set <filesystem name> <var> <val>
35
36::
37
38 fs add_data_pool <filesystem name> <pool name/id>
39
40::
41
42 fs rm_data_pool <filesystem name> <pool name/id>
43
44
31f18b77
FG
45Settings
46--------
47
48::
49
50 fs set <fs name> max_file_size <size in bytes>
51
52CephFS has a configurable maximum file size, and it's 1TB by default.
53You may wish to set this limit higher if you expect to store large files
54in CephFS. It is a 64-bit field.
55
56Setting ``max_file_size`` to 0 does not disable the limit. It would
57simply limit clients to only creating empty files.
58
59
60Maximum file sizes and performance
61----------------------------------
62
63CephFS enforces the maximum file size limit at the point of appending to
64files or setting their size. It does not affect how anything is stored.
65
66When users create a file of an enormous size (without necessarily
67writing any data to it), some operations (such as deletes) cause the MDS
68to have to do a large number of operations to check if any of the RADOS
69objects within the range that could exist (according to the file size)
70really existed.
71
72The ``max_file_size`` setting prevents users from creating files that
73appear to be eg. exabytes in size, causing load on the MDS as it tries
74to enumerate the objects during operations like stats or deletes.
75
76
7c673cae
FG
77Daemons
78-------
79
80These commands act on specific mds daemons or ranks.
81
82::
83
224ce89b 84 mds fail <gid/name/role>
7c673cae 85
224ce89b
WB
86Mark an MDS daemon as failed. This is equivalent to what the cluster
87would do if an MDS daemon had failed to send a message to the mon
88for ``mds_beacon_grace`` second. If the daemon was active and a suitable
89standby is available, using ``mds fail`` will force a failover to the standby.
90
91If the MDS daemon was in reality still running, then using ``mds fail``
92will cause the daemon to restart. If it was active and a standby was
93available, then the "failed" daemon will return as a standby.
7c673cae
FG
94
95::
96
97 mds deactivate <role>
98
224ce89b
WB
99Deactivate an MDS, causing it to flush its entire journal to
100backing RADOS objects and close all open client sessions. Deactivating an MDS
101is primarily intended for bringing down a rank after reducing the number of
c07f9fc5
FG
102active MDS (max_mds). Once the rank is deactivated, the MDS daemon will rejoin the
103cluster as a standby.
104``<role>`` can take one of three forms:
105
106::
107
108 <fs_name>:<rank>
109 <fs_id>:<rank>
110 <rank>
224ce89b
WB
111
112Use ``mds deactivate`` in conjunction with adjustments to ``max_mds`` to
113shrink an MDS cluster. See :doc:`/cephfs/multimds`
114
7c673cae
FG
115::
116
117 tell mds.<daemon name>
118
119::
120
121 mds metadata <gid/name/role>
122
123::
124
125 mds repaired <role>
126
127
128Global settings
129---------------
130
131::
132
133 fs dump
134
135::
136
137 fs flag set <flag name> <flag val> [<confirmation string>]
138
139"flag name" must be one of ['enable_multiple']
140
141Some flags require you to confirm your intentions with "--yes-i-really-mean-it"
142or a similar string they will prompt you with. Consider these actions carefully
143before proceeding; they are placed on especially dangerous activities.
144
145
146Advanced
147--------
148
149These commands are not required in normal operation, and exist
150for use in exceptional circumstances. Incorrect use of these
151commands may cause serious problems, such as an inaccessible
152filesystem.
153
154::
155
156 mds compat rm_compat
157
158::
159
160 mds compat rm_incompat
161
162::
163
164 mds compat show
165
166::
167
168 mds getmap
169
170::
171
172 mds set_state
173
174::
175
176 mds rmfailed
177
178Legacy
179------
180
31f18b77
FG
181The ``ceph mds set`` command is the deprecated version of ``ceph fs set``,
182from before there was more than one filesystem per cluster. It operates
183on whichever filesystem is marked as the default (see ``ceph fs
184set-default``.)
185
7c673cae
FG
186::
187
188 mds stat
189 mds dump # replaced by "fs get"
190 mds stop # replaced by "mds deactivate"
191 mds set_max_mds # replaced by "fs set max_mds"
192 mds set # replaced by "fs set"
193 mds cluster_down # replaced by "fs set cluster_down"
194 mds cluster_up # replaced by "fs set cluster_up"
195 mds newfs # replaced by "fs new"
196 mds add_data_pool # replaced by "fs add_data_pool"
197 mds remove_data_pool #replaced by "fs remove_data_pool"
198