[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gfarm-announce:90922] Gfarm version 2.4.0 released

Hi all,

We are pleased to announce the release of Gfarm file system version


This is a major upgrade.  It supports update-based replica consistency
management that keeps the number of file replicas when modified.
Also, it fixes the data race between creating a new file replica and
deleting the old one that may cause data loss in quite a rare case.

When you upgrade to this version, we recommend to upgrade all
components including gfmd, all gfsds and all clients.  Note that some
features available in the version 2.3.2 are not available in this
version, which will be included in version 2.4.1.  Refer to the
release note.

Release note for Gfarm 2.4.0


New Feature
* update-based replica consistency protocol
  that keeps number of file replicas at file modification

New configuration in gfmd.conf
* simultaneous_replication_receivers directive to specify the maximum
  number of pending replication requests to each gfsd

* how to access Gfarm via samba from Windows clients

Updated feature
* gfwhere - several options to obtain in progress or obsolete replica

Bug fix
* fix possibility to lost files in a rare case when updating and
  replicating at the same time
* gfhost -R does not work [sf.net trac #120]
* retry another file system node in GFARM_ERR_FILE_MIGRATED case
  [sf.net trac #117]
* fix errors found by static analysis including unchecked return value
  and missing check against null
* compilation failure with old OpenLDAP library since the version
  2.3.0 [sf.net trac #121]
* compilation failure on Linux 2.4 since the version 2.3.0
  [sf.net trac #122]

Not supported
* no_file_system_node_timeout and gfmd_reconnection_timeout directives
  to specify the timeout to try to find a file system node and to
  reconnect to the gfmd, respectively.  Default is 30 seconds.
* gfmd - check and repair nlinks at start-up
* gfsd - if the input/output error occurs, kill oneself to cope with
  the hardware failure
* select a file system node having enough capacity regardless of
  existent file replicas when a file is overwritten

Osamu Tatebe
Department of Computer Science, University of Tsukuba
1-1-1 Tennodai, Tsukuba, Ibaraki 3058577 Japan