mhddfs(1)

✨ NAME ✨

mhddfs — bestie, it's literally the driver that combines a several mount points into the single one. 💅

---

🌸 SYNOPSIS 🌸

okay so here's the vibe, the shape of it, no cap:

mhddfs /dir1,/dir2[,/path/to/dir3] /path/to/mount [-o options]
mhddfs /dir1 dir2,dir3 /mount/point [-o options]
...
fusermount -u /path/to/mount

🎀 fstab record example:

if you're the kind of girl who lives in /etc/fstab (iconic, honestly), it looks like this:

mhddfs#/path/to/dir1,/path/to/dir2 /mnt/point fuse defaults 0 0

mhddfs#/dir1,/dir2,/dir3 /mnt fuse logfile=/var/log/mhddfs.log 0 0

---

👑 OPTIONS 👑

with an -o option1,option2... you can specify some additional options. yes bestie, comma-separated, just like that. 🫶

• logfile=/path/to/file.log — point this at a file and that file will contain debug information. a little diary for your filesystem, if you will. 📓
• loglevel=x — how chatty do we want it? pick your level:
  • 0 — debug messages
  • 1 — info messages
  • 2 — standard (default) messages
• mlimit=size[m|k|g] — this is the free space size threshold, and it's lowkey the whole personality of this tool. if a drive has free space less than the threshold specified, then another drive will be choosen while creating a new file. and if all the drives have free space less than the threshold specified, then the drive containing the most free space will be choosen. 💖

Default value is 4G, minimum value is 100M. don't try to go lower, she said what she said.

This option accepts suffixes:

• [mM] — megabytes
• [gG] — gigabytes
• [kK] — kilobytes

For an information about the additional options see output of:

mhddfs -h

---

🦋 DESCRIPTION 🦋

The file system allows to unite a several mount points (or directories) to the single one. So a one big filesystem is simulated and this makes it possible to combine a several hard drives or network file systems. This system is like unionfs but it can choose a drive with the most of free space, and move the data between drives transparently for the applications. it's giving main character energy, fr fr. ⭐

While writing files they are written to a 1st hdd until the hdd has the free space (see mlimit option), then they are written on a 2nd hdd, then to 3rd etc. it just keeps going, she never runs out of room. 🧚

df will show a total statistics of all filesystems like there is a big one hdd. one big hdd, one big slay.

If an overflow arises while writing to the hdd1 then a file content already written will be transferred to a hdd containing enough of free space for a file. The transferring is processed on-the-fly, fully transparent for the application that is writing. So this behaviour simulates a big file system. no cap, the app writing the file has no idea it just got relocated. 😭✨

💀 WARNINGS 💀

The filesystems are combined must provide a possibility to get their parameters correctly (e.g. size of free space). Otherwise the writing failure can occur (but data consistency will be ok anyway). For example it is a bad idea to combine a several sshfs systems together. like, genuinely, don't. 🙈

Please read FUSE documentation for a further conception. seriously bestie, go read it, iykyk.

---

💜 COPYRIGHT 💜

Distributed under GPLv3

Copyright (C) 2008 Dmitry E. Oboukhov <dimka@avanto.org>

---

and that's the whole page, bestie!! 🌈✨ this one's from the General Commands Manual, mhddfs(1), dated February 2008 — shoutout to the icon who wrote it down for us. go forth and unite those mount points. periodt. 💅🎀🦋