« Changelog History


MooseFS v3.0.107 Release Notes

Release Date: 2019-11-11 // over 4 years ago

  • Dear MooseFS Users,
    Long-awaited MooseFS 3.0.107 is now stable!

    This release is mainly a bugfix release (and includes a lot of fixes). We strongly recommend to upgrade to this latest version! This release also introduces some new features, including support for libfuse3.

    🚀 We would like to thank all the contributors who helped us making this release, especially (alphabetically): @eleaner, @hradec, @itongqingbo, @njaard, @onlyjob, @steffenb7333. Thank you for all your help!

    (If I forgot to mention somebody, I am very sorry and please let me know!)

    🚀 Please find the list of fixes and new features that this release includes below:

    • (master) added NOP command to changelog
    • (master+supervisor) added time check
    • 👷 (cs) fixed behaviour when job queue is full
    • (cli+cgi) added time data to master servers
    • 🛠 (cs) fixed NOP packets ping-pong
    • 🛠 (client) fixed NOP flooding in write module
    • 👷 (cs) fixed race condition in bgjobs module (jobhash)
    • 👍 (cs+mount) added new status returned to mount when queue is full and support for it in client module
    • 👍 (mount) added initial support for libfuse3 (related to issue #302)
    • 👍 (mount) added support for readdirplus (related to issue #302)
    • ↪ (mount) workaround for bug in fuse (wrong lock_owner in flush – issue #305)
    • 🛠 (mount) fixed deadlock in readdata.c (closes issue #306)
    • ✅ (mount+master) fixed few small issues related to POSIX compliance (checked by pjd fstest)
    • ✅ (all) changed preferred C standard from C99 to C11 and added tests for atomics
    • 🚚 (mount) move read/write structures initialization from open to read/write
    • (mount,mfsio) added new inode->fleng map
    • 🔧 (configure) added option disable_all, added summary at the end
    • (freebsd) detecting new fuse version in the kernel and adjusting behaviour
    • 👍 (tools) better handling of unrecognized options
    • 👍 (master) better hard links handling
    • (master) added limit for number of hardlinks allowed for one object
    • (master) added option for automatic removal of unused chunkservers (issue #247)
    • 🛠 (metadirinfo) fixed segfault when output filename is not specified
    • (chunktool) added file name fixing option (issue #276)
    • (all) changed chunk replication and deletion charts into two-color charts (successful/unsuccessful – issue #273)
    • (all) added new charts with number of chunk creations and internal changes (also successful and unsuccessful)
    • (master) added ignoring chunk with id zero sent from chunkserver
    • 📇 (metadump) added option for dumping parts of metadata
    • 🔊 (master) added more logs to background data write subprocess (related to issue #280)
    • 🛠 (master) fixed LEADER/FOLLOWER desync on SETCHUNK command (pro only)
    • 🔧 (cli+cgi) fixed shebang in python scripts (preference for python3 in configure)
    • (master) changed pipe in bgsaver to nonblocking mode
    • (master) added check if the background saving process is alive
    • (master) added lockfile for background saving process
    • 🆓 (master) added protection against time going back in the free inodes list
    • (master) added protection in FOLLOWER against not keeping up with the LEADER (pro only)
    • (master) changed condition for removing chunk from data structures (all chunkservers have to be connected)
    • ⏪ (master) added restore run mode (works similar to mfsmaster -a but without running daemon)
    • (master) take write replication counters into account in server ordering for new chunk creations
    • (master) changed calculating replication limits in chunk rebalance procedure (using actual usage difference)

    Best regards,
    Piotr / MooseFS Team