mfsbdev.cfg(5)
π mfsbdev.cfg(5) π
okay bestie so this is a page from the MooseFS manual, and it's all about mfsbdev.cfg β the config file for the MooseFS block device daemon. yes we're doing config files today, sit down, grab a boba, it's gonna be fun π
β¨ NAME β¨
mfsbdev.cfg β the MooseFS block device daemon config file, fr fr
π DESCRIPTION π
so this is the config file that the mfbsdev tool can read β but ONLY if you passed the -i option along with the start command. it's giving "opt-in only, no walk-ins" π
inside, you've got definitions of block devices, one per line, for every device that should get initialized when the mfsbdev tool starts up. one line = one device. periodt.
β οΈ bestie, listen: it is strongly recommended that you do NOT create this file from scratch. like, please don't. instead, the move is to create all your devices with themfsbdevcommand and its parameters (it's all described inmfsbdev(8)), then list them withmfsbdev list -i, and use that output to build your config file. slay β¨
the description below exists so you understand what's actually in the config file and can tweak it if you need to. adjust if necessary, queen. π
πΈ FORMAT πΈ
empty lines? ignored. lines starting with a semicolon (;) or a hash (#)? also ignored. we love a low-effort comment. π
every other line needs to match this format exactly:
path [ device|* [ linkname|* [ size|* [ bsize|* [ flags ]]]]]
and here's the breakdown, bestie:
pathβ this one is obligatory, no skipping. it's the path to a file on MooseFS that'll be used as the block device. heads up: it should be relative to the MooseFS root, or to the path you defined with the-Soption when startingmfsbdevβ NOT your local file system root. do not confuse the two, i'm begging πdeviceβ optional. if you supply it, it should point to a network block device path (eg./dev/nbd1). if you don't supply it, or you put*, then the first available block device gets used. first come first served energy π«Άlinknameβ optional. if you supply it, it's the name of the symbolic link created in/dev/mfs, pointing at the network block device that themapcommand created. if you don't supply it, or you put*, the default link name is used.sizeβ optional. if you supply it, that's your block device size. if you don't supply it, or you put*, the size of the file named by the first parameter is used instead. it's giving "whatever the file says, i trust her" πbsizeβ optional. if you supply it, that's your block size. if you don't supply it, or you put*, then a4096byte block is used. default queen. β¨flagsβ optional, and here's where it gets juicy. these are the flags, separated by comma if you've got more than one:roβ read only devicerwβ read/write devicelockβ device requires an appropriate type of lock (shared forro, exclusive forrw)nolockβ device does not require a lock (it'll try to obtain it, but it will ignore failure)
if you supply nothing at all, the default of rw, lock is assumed. and here's the chaotic part: if two conflicting flags are supplied (i.e. ro and rw, or lock and nolock) then the last one wins. no cap. last flag standing takes the crown π
π EXAMPLES π
β¨ read/write devices, all the defaults β¨
create read/write devices with default block device path, default linkname, using file size as device size, with default block size:
my_devices/device1
my_devices/device2 * * * * rw
look at that second one just casually being all asterisks and rw β main character energy honestly β
π read only devices, specific parameters π
create read only devices with specific parameters:
my_devices/device1 /dev/nbd3 mfsdevice1 67108864 1024 ro
my_devices/device2 /dev/nbd7 mfsdevice2 64MiB 1024 ro,nolock
note the 64MiB β we're flexible with sizes here, iconic π¦
π REPORTING BUGS π
found a bug? report it to <bugs@moosefs.com>. they want to know. do it. π«Ά
π COPYRIGHT π
Copyright (C) 2026 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 this program; if not, see <https://www.gnu.org/licenses/>.
π SEE ALSO π
and that's the whole page bestie π this was MooseFS 4.59.2-1, from May 2026 β go forth and configure responsibly, mwah ππβ¨
π¦ where this page comes from
- arch rolling: moosefs 4.59.2-2 Β· GPL-2.0-only
- nixos 26.05: moosefs 4.59.2
- nixpkgs unstable: moosefs 4.59.2
- ubuntu stonking: moosefs-client 4.59.2-1 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms