It took us quite a long time to publish the next version of MooseFS :) And it happened that we had not officially published 1.6.18 to the public at all and now 1.6.19 is available.
 
1.6.18 had some substantial changes to the metalogger so that the metadata are sent upon its startup and overall integrity of metadata is kept when the metalogger crashes and then restarts. We also added some other features and made bug fixes based on the feedback from the community. And here special thanks go to Thomas Hatch who thoroughly beta tested 1.6.18 :)
 
Detailed list of changes include:

• (metalogger) added sending metadata after metalogger startup
• (master, metalogger) added sending two change logs together with metadata
• (metarestore) improved merging change logs
• (all) added a lot of assertions (mainly NULL pointers, and unsuccessful thread functions)
• (all) fixed some minor bugs and potential race conditions (makes valgrind happy)
• (cs) added ability to use read-only disks in "marked for removal" mode (to retrieve missing chunks from damaged disks)
• (cs) added showing scanning progress during startup
• (all/master) added releasing used resources at the end
• (all) changed some malloc/free allocations into mmap/munmap
• (all) new error messages routines
• (daemons) added proper handling SIGINT in "foreground" mode
• (cgiserv) fixed small bug (malformed request could crash cgiserv)

 
 
1.6.19 contains lots of further improvements and here special thanks go to Christopher Lewis and Davies Liu. The complete list of changes:
 

• (debian) separated mfs-common and mfs-metalogger subpackages, added init scripts (contributed by Christopher Lewis)
• (daemon) fixed return values (return non zero on error)
• (cs) fixed chunk testing bug (any error during chunk opening caused assigning whole disk as damaged)
• (cs,metalogger) added resolving master name when connection failed (patch contributed by Davies Liu)
• (mount) added creating new session when previous is lost (inspired by Davies Liu)
• (cs) added for unused chunks week delay before deletion (inspired by Davies Liu)
• (cgi) added switching between name and IP in 'path' column in 'Disks' table (inspired by Davies Liu)
• (master) do not update ctime when goal, trashtime or extra attributes are not changing

 
And one important thing - the recommended order of upgrading process is: master server -> metalogger(s) -> chunkservers -> client mounts.