second OpenAFS 1.6.12 release candidate available

The OpenAFS 1.6 Release Team is pleased to announce that the second =
1.6.12
release candidate, 1.6.12pre2, has been tagged in the OpenAFS source =
repository,
available at:

  git://git.openafs.org/openafs.git

as tag: "openafs-stable-1_6_12pre2".

Source files and available binaries can be accessed via the web at:

  http://dl.openafs.org/dl/candidate/1.6.12pre2/

or via AFS at:

  UNIX: /afs/grand.central.org/software/openafs/candidate/1.6.12pre2/
  UNC: \\afs\grand.central.org\software\openafs\candidate\1.6.12pre2\

There are no binaries yet. Those will be uploaded as they become =
available.

Besides a few other minor fixes and enhancements, these are the major =
change
with respect to the 1.6.11.1 release:

 * [new in pre2] Support for Linux kernels up to 4.1 (confirmed for =
4.1-rc4)

 * [new in pre2] Avoid spurious EIO errors when writing large chunks of =
data
   to mmapped files on Linux

 * Avoid potential Ubik database corruption

   When a database server is shut down and then restarted with an empty =
or
   altered database before the sync site has a chance to notice the =
restart,
   it is possible for the restarted server's database to become =
corrupted
   and yet labeled "current".  With pre-1.6.12 releases the sync site =
requires
   up to 75 seconds to notice that a server has been restarted. The =
corrupted
   database will be used to answer client queries and can be propagated =
to other
   database servers.

   This problem has always existed, but became easier to trigger with =
modern
   server deployment techniques and faster hardware.


For the full list of user visible changes foreseen for 1.6.12, please =
see

  http://dl.openafs.org/dl/candidate/1.6.12pre2/RELNOTES-1.6.12pre2


Please assist us by deploying this prerelease and providing positive or
negative feedback. Bug reports should be filed to =
[email protected] .
Reports of success should be sent to [email protected] .

1.6 releases are no longer targeting Microsoft Windows.