mfsarchive(1)

πŸ“¦
version 4.59.2 Β· 5 versions
, in arch rolling, nixos 26.05, nixpkgs unstable, ubuntu stonking

✨ mfsarchive β€” MooseFS archive storage mode management tools ✨

okay bestie, come SIT. this is mfsarchive, part of the MooseFS family, and it's lowkey one of the most useful little squads of tools you'll ever meet. it's giving "tiny commands, big power" fr fr πŸ’…


🌸 SYNOPSIS 🌸

mfschkarchive [-?] [-n|-h|-H|-k|-m|-g] OBJECT...

mfsclrarchive [-?] [-n|-h|-H|-k|-m|-g] OBJECT...

mfssetarchive [-?] [-n|-h|-H|-k|-m|-g] OBJECT...

three little icons, one shared vibe check. every one of them takes the same options and the same OBJECT... list, so once you know one you know all three. no cap. πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

so like, these tools all mess with one specific thing: the archive bit of a filesystem object. and "object" here means a file, a special file, or a directory. that's the whole target audience. 🫢

here's the tea on what that bit even does: normally it gets set automatically, following whatever the storage class definition says β€” that's the ARCH_DELAY situation. and then, depending on where the bit stands:

  • if the archive bit is set, then ARCH_LABELS from the storage class definition get used ✨
  • otherwise, KEEP_LABES are used πŸ’–

(yes, the original spells it KEEP_LABES. we do not fix. we do not touch. we just love it. iconic behavior honestly.)

now, the three besties themselves:

  • mfschkarchive β€” prints the current archive bit value of the given object(s). and if the OBJECT you hand it is a DIRECTORY? it prints the current archive bit value of all the contained files, recursively. it's thorough like that. πŸ’…
  • mfsclrarchive and mfssetarchive β€” these two clear and set (in that order, respectively) the current archive bit of the given object(s). and just like mfschkarchive: if OBJECT is a DIRECTORY, then the tool goes recursive. same energy, different direction.
heads up bestie: recursive means recursive. point them at a directory and they will absolutely walk the whole tree. that's not a bug, that's the design, but know it before you type it. 😭

πŸ’œ OPTIONS πŸ’œ

first, the group chat announcement: most MooseFS tools use -n, -h, -H, -k, -m and -g to pick the format of printed numbers. so let's go through the whole lineup, one by one:

  • -n β€” prints exact numbers. plain, honest, no dressing. the default vibe.
  • -h β€” uses binary prefixes: Ki, Mi, Gi, standing for 2^10, 2^20, etc. 🌈
  • -H β€” uses SI prefixes: k, M, G, standing for 10^3, 10^6, etc. ⭐
  • -k β€” shows plain numbers in kibis (binary kilo β€” 1024) πŸŽ€
  • -m β€” shows plain numbers in mebis (binary mega β€” 1024^2) πŸ¦‹
  • -g β€” shows plain numbers in gibis (binary giga β€” 1024^3) πŸ‘‘
  • -? β€” displays the short usage message. your lil "help me" button. πŸ™ˆ

and if flags aren't your thing (valid), you can get the exact same result by setting the MFSHRFORMAT environment variable instead. here's the mapping, write it down:

  • 0 β€” exact numbers
  • 1 or h β€” binary prefixes
  • 2 or H β€” SI prefixes
  • 3 or h+ β€” exact numbers and binary prefixes
  • 4 or H+ β€” exact numbers and SI prefixes

the default is to print just exact numbers. so if you do nothing, you get exact numbers, and honestly? respecting that. πŸ’–


πŸ“ REPORTING BUGS πŸ“

found a bug? don't suffer in silence bestie, tell the devs:

bugs@moosefs.com


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!! you read it, you understood it, you're basically a MooseFS archivist now 🧚 this was MooseFS 4.59.2-1, dated May 2026 β€” so go forth, check those archive bits, set those archive bits, clear those archive bits, and slay πŸ’…βœ¨

πŸ“¦ where this page comes from