[Bug 246416] sysutils/moosefs3-master: Update to 3.0.113

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246416

            Bug ID: 246416
           Summary: sysutils/moosefs3-master: Update to 3.0.113
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://github.com/moosefs/moosefs/releases/tag/v3.0.1
                    13
                OS: Any
            Status: New
          Keywords: easy, patch, patch-ready
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: freebsd at moosefs.pro
                CC: lifanov at freebsd.org, tcberner at freebsd.org
 Attachment #214413 maintainer-approval+
             Flags:

Created attachment 214413
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=214413&action=edit
Update MooseFS to the latest stable version (3.0.113-1)

The master port will update all the moosefs3-* related ports as well.

This change in ports passes QA (portlint, poudriere).

This change fixes MooseFS ports issues that were found in bug 245041
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245041)

Thank you,
Piotr / MooseFS Team

Recent changes since MooseFS 3.0.112:

* MooseFS 3.0.113-1 (2020-05-04)

  - (master) removed unnecessary debug syslog messages
  - (check) increased usleep tolerance due to some operating systems (issue
#351)
  - (master) changed condition that decides if master should wait for more
chunks during I/O
  - (mount) delayed setting channel for fuse notifications (very rare segfault
in libfuse2 during init)
  - (client+master) changed conditions for ancestor test in getattr (issue
#350)
  - (cs) added parameter for number of chunks to be send in single register
packet
  - (cs) fixed reporting damaged chunks in testing function (issue #352)
  - (cs) removed some unnecessary damaged chunk notifications
  - (client) changed open test in setattr (related to issue #350)
  - (master) fixed handling truncate for open files (related to issue #350)
  - (master) added uid mapping in setfacl function
  - (master+client) added support for atomic truncate with open
  - (master+client) fixed keep cache conditions
  - (cs) introduced official label format defined in chunkserver configuration
  - (nbd) added readonly mode and locking
  - (cs) fixed condition in choosing disks for internal rebalance
  - (mount) added workaround in access for a bug in FreeBSD kernel (issue #354)
  - (cs) fixed master reconnection conditions (reload usually shouldn't cause
reconnection)
  - (freebsd) fixed FreeBSD port (makeports.sh)
  - (master) changed disk removal detection algorithm (issue #356)
  - (cs) fixed calculating size limits
  - (cs) added handling inode limits in local filesystems on chunkservers
(issue #358)
  - (master) added topology grouping when new chunks are about to be created
(prefer closer servers)
  - (master) added more error messages to bgsaver
  - (cs) added changing subfolder during internal rebalance (related to issue
#326)
  - (master+cs) added optional logging of long function execution times
  - (all) fixes of small errors found by static code analysers
  - (mount) turn off dentry invalidator for Linux kernels >= 4.19 (related to
issue #357)
  - (master) changed condition that checks timestamp in changelogs (less prone
to small clock differences)
  - (daemons) added time refresh function (for future use)
  - (cgi+cli) changed mark for removal state name UNKNOWN->PENDING (related to
issue #359)
  - (client) decreased max IDLE time in writer module from 1s to 0.1s
  - (client) update inode in dentry invalidator
  - (tools) fixed mfscopyeattr, mfsseteattr and mfs*arch tools
  - (master+client) added support for new eattrs: immutable, appendonly,
undeletable (setting new undeletable extra attribute appropriately can help
with issues like #357)
  - (client) silenced "kern.proc.filedesc" syslog messages on FreeBSD (issue
#360)

-- 
You are receiving this mail because:
You are the assignee for the bug.