mfsstatsdump(8) This is part of MooseFS mfsstatsdump(8)

mfsstatsdump - dump usage data from master stats file in csv or png format

mfsstatsdump -f fields [-i stats_file] [-r range] [-s separator] [-p png_filename [-x chart_width] [-y chart_height]] [-hHd]

mfsstatsdump dumps usage data from master stats file. These are the same data sets that are used to make CGI charts. Output can be either in text format (csv) or in graphical format (png). That means -p, -x and -y options are mutually exclusive with -h, -H and -d options.

MooseFS master server saves the stats file in the DATA_PATH directory - see mfsmaster.cfg(5)

field names separated by ',' (see FIELDS section); at least one field is mandatory; if an asterisk (*) is used, all fields are dumped
name of mfs binary stats file (default: default_data_path/stats.mfs)
range type: 0 - short range (minute) 1 - medium range (6 minutes) 2 - long range (30 minutes) 3 - very long range (day)
specify column separator (default: tabulator)
optional PNG filename (field name will be added before .png; YYYY -> YYYY_FIELD.png, YYYY.png -> YYYY_FIELD.png)
PNG chart width (default: 1600)
PNG chart height (should be divisible by 20 - if not then it will be adjusted; default:320)
"human-readable" numbers using base 2 prefixes (IEC 60027)
"human-readable" numbers using base 10 prefixes (SI)
show timestamps in YYYY-MM-DD HH:MM format

User cpu usage
System cpu usage
Total cpu usage (in csv sum of scpu and ucpu, in png shows both in different colors)
Number of chunk deletions
Number of chunk replications
Number of statfs operations
Number of getattr operations
Number of setattr operations
Number of lookup operations
Number of mkdir operations
Number of rmdir operations
Number of symlink operations
Number of readlink operations
Number of mknod operations
Number of unlink operations
Number of rename operations
Number of link operations
Number of readdir operations
Number of open operations
Number of read operations
Number of write operations
Received packets
Sent packets
Received bytes
Sent bytes
Resident memory usage
Virtual memory usage
Total memory usage (in csv is the same as memoryvirt, in png shows both memoryrss and memoryvirt using two colors)
Used raw disk space
Total raw disk space
Total raw disk space (in csv the same as totalspace, in png shows both usedspace and totalspace using two colors)
Number of chunk_read operations
Number of chunk_write operations
Number of chunk creation attempts
Number of chunk internal operation attempts
Number of successful chunk deletions
Number of unsuccessful chunk deletions
Sum of succesful and unsuccessful chunk deletions (in png shows both delete_ok and delete_err using two colors)
Number of successful chunk replications
Number of unsuccessful chunk replications
Sum of succesful and unsuccessful chunk replications (in png shows both replicate_ok and replicate_err using two colors)
Number of successful chunk creations
Number of unsuccessful chunk creations
Sum of succesful and unsuccessful chunk creations (in png shows both create_ok and create_err using two colors)
Number of successful chunk internal operations
Number of unsuccessful chunk internal operations
Sum of succesful and unsuccessfulchunk internal operations (in png shows both change_ok and change_err using two colors)
Number of successful chunk split operations
Number of unsuccessful chunk split operations
Sum of succesful and unsuccessful chunk split operations (in png shows both split_ok and split_err using two colors)
Number of file objects
Number of non-file objects (directories,symlinks,etc.)
Number of all objects (in png shows both fileobjects and metaobjects using two colors)
Total number of chunks stored in EC8 format
Total number of chunks stored in EC4 format
Total number of chunks stored in COPY format
Total number of chunks stored in any format (in png shows chunksec8, chunksec4 and chunkscopy using three colors)
Number of endangered chunks (mark for removal excluded)
Number of undergoal chunks (mark for removal excluded)
Number of endangered and undergoal chunks (mark for removal excluded, in png shows chregdanger and chregunder using two colors)
Number of endangered chunks (mark for removal included)
Number of undergoal chunks (mark for removal included)
Number of endangered and undergoal chunks (mark for removal included, in png shows challdanger and challunder using two colors)
Average number of bytes read per second by all clients
Average number of bytes written per second by all clients
Number of fsync operations
Number of lock operations
Number of snapshot operations
Number of truncate operations
Number of getxattr operations
Number of setxattr operations
Number of getfacl operations
Number of setfacl operations
Number of file create operations
Number of extra metadata operations (sclass,trashretention,eattr etc.)
(pro only) Master max delay in seconds
Number of all registered chunk servers (both connected and disconnected)
Number of all disconnected chunk servers
Number of disconnected chunk servers that are in maintenance mode
Number of all registered chunk servers (in csv equals to servers, in png shows servers, dservers and mdservers using three different colors)
Difference in space usage percent between the most and least used chunk server

Text output - text (csv) file where first column is a timestamp (or date if -d option was specified), the following column are what was specified with the -f options, formatted according to used options (none, -s and -h or -H)

Graphical output - one png file with a chart is created for every field specified with the -f option, according to the naming scheme declared with the -p option. Size may be adjusted with -x and -y options.

Data sets delete and delete_stat in a properly working system should be roughly the same, but not always identical (in their CSV form), this stems from the fact that the delete set is calculated using the number of requests sent by the master, and the delete_stat set is calculated using the number of replies received from chunk servers, so local fluctuations may be observed (i.e. one minute has more sent requests - higher value in the delete set and the next minute has more answers - higher value in delete_stat set). But if one were to calculate the sum of differences between the two sets over time, this sum should never grow over a certain number.

However, if there is some kind of problem (with network communication and/or chunk server process(es)) and some chunk delete requests are stalled/go missing, then delete values may be constantly higher than the delete_stat values and the sum of differences between the two sets will be steadily growing over time.

Same goes for replicate(_stat), create(_stat), change(_stat) and split(_stat) data sets.

Report bugs to <bugs@moosefs.com>.

Copyright (C) 2024 Jakub Kruszona-Zawadzki, Saglabs SA

This file is part of MooseFS.

MooseFS 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 2 (only).

MooseFS 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 MooseFS; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02111-1301, USA or visit http://www.gnu.org/licenses/gpl-2.0.html

mfsmount(8), moosefs(7)

September 2024 MooseFS 4.56.6-1