LIZARDFS-ADMIN(8)

📦 version 3.12.0, in fedora 43

💖 LIZARDFS-ADMIN(8) 💖

okay bestie, sit down, hydrate, because today we're getting into lizardfs-admin and lizardfs-probe — the monitoring and administration tool for LizardFS. yes, that's the manual page name up there in the corner, and yes, it's giving sysadmin main character energy. let's go 🦋

✨ NAME ✨

lizardfs-admin, lizardfs-probe — LizardFS monitoring and administration tool

no cap, that's literally it. this is your remote control for the whole installation, and it's lowkey iconic.

🌸 SYNOPSIS 🌸

lizardfs-admin COMMAND [OPTIONS...] [ARGUMENTS...]

you pick a COMMAND, you toss in some OPTIONS, you feed it the ARGUMENTS. that's the whole vibe. 💅

👑 AVAILABLE COMMANDS 👑

okay so this is the menu, and bestie it is a menu. every single one, right here:

🍓 chunks-health <master ip> <master port>

Returns chunks health reports in the installation. By default (if no report is specified) all reports will be shown. In replication and deletion states, the column means the number of chunks with number of copies specified in the label to replicate/delete.

possible command-line options:

  • --availability — print report about availability of chunks.
  • --replication — print report about about number of chunks that need replication.
  • --deletion — print report about about number of chunks that need deletion.
not me noticing the original says "about about" twice and keeping it anyway 💀 details are details, bestie, i don't make the rules. i just preserve them.

🍓 info <master ip> <master port>

Prints statistics concerning the LizardFS installation.

🍓 iolimits-status <master ip> <master port>

Prints current configuration of global I/O limiting

🍓 list-chunkservers <master ip> <master port>

Prints information about all connected chunkservers.

🍓 list-disks <master ip> <master port>

Prints information about all connected chunkservers.

possible command-line options:

  • --verbose — be a little more verbose and show operations statistics.

🍓 list-goals <master ip> <master port>

List goal definitions.

possible command-line options:

  • --pretty — print nice table

🍓 list-mounts <master ip> <master port>

Prints information about all connected mounts.

possible command-line options

  • --verbose — be a little more verbose and show goal and trash time limits.

🍓 metadataserver-status <master ip> <master port>

Prints status of a master or shadow master server

🍓 list-metadataservers <master ip> <master port>

Prints status of active metadata servers.

🍓 ready-chunkservers-count <master ip> <master port>

Prints number of chunkservers ready to be written to.

🍓 promote-shadow <shadow ip> <shadow port>

Promotes metadata server. Works only if personality ha-cluster-managed is used. Authentication with the admin password is required.

🔥 heads up: only works with the ha-cluster-managed personality, and you need the admin password. no password, no promotion, periodt.

🍓 stop-master-without-saving-metadata <master ip> <master port>

Stop the master server without saving metadata in the metadata.mfs file. Used to quickly migrate a metadata server (works for all personalities). Authentication with the admin password is required.

😭 the name literally says it — it stops the master without saving metadata. it's for quick metadata server migration, it works for all personalities, and again: admin password required.

🍓 reload-config <master ip> <master port>

Requests reloading configuration from the config file. This is synchronous (waits for reload to finish). Authentication with the admin password is required.

🧚 synchronous means it waits. it will not leave you on read. admin password required, as ever.

🍓 save-metadata <metadataserver ip> <metadataserver port>

Requests saving the current state of metadata into the metadata.mfs file. With --async fail if the process cannot be started, e.g. because the process is already in progress. Without --async, fails if either the process cannot be started or if it finishes with an error (i.e., no metadata file is created). Authentication with the admin password is required.

possible command-line options:

  • --async — don't wait for the task to finish.
💖 so real talk: with --async it only fails if the process can't start (like if one's already running). without --async it also fails if the thing finishes with an error, i.e. no metadata file got created. and yes — admin password required. always the admin password.

🌈 COMMON COMMAND OPTIONS 🌈

  • --porcelain — make the output parsing-friendly.

that's the one that works across commands, bestie. machine-readable glow-up ✨

2013-2015 Skytechnology sp. z o.o.

LizardFS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 3.

LizardFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with LizardFS. If not, see http://www.gnu.org/licenses/.

aaaand that's the whole page, bestie 🫶 this edition is dated 07/24/2025, and it lives under the manual name LIZARDFS-ADMIN(8) — go forth and monitor your installation like the icon you are 👑

📦 where this page comes from