OpenAFS 1.6.11 release available
Stephan Wiesand <[email protected]> Mon, 2 Mar 2015 18:07:42 +0100
| Newsgroups | gmane.comp.file-systems.openafs.announce |
|---|---|
| Message-ID | <[email protected]> |
The OpenAFS Release Team is pleased to announce the availability of = OpenAFS version 1.6.11 for UNIX/Linux. Source files can be accessed via the web = at: http://www.openafs.org/dl/openafs/1.6.11/ or via AFS at: /afs/grand.central.org/software/openafs/1.6.11/ \\afs\grand.central.org\software\openafs\1.6.11\ There are no binaries yet. Those will be uploaded as they become = available. OpenAFS 1.6.11 is the next in the current series of stable releases of = OpenAFS for all platforms except Microsoft Windows. This release is focused on = relatively few client side fixes and platform support: * Support for recent Linux kernels up to 3.19 Note that kernels 3.17 to 3.17.2 require an additional configure = switch when building the kernel module in order to work correctly. The same = could apply to distribution kernels with backports of certain changes from = 3.17 but not the corresponding fix from 3.17.3 / 3.18. Please consult the release notes and the README for details. * Support for OS X 10.10 "Yosemite" (there's no installer though) * Build support for FreeBSD >=3D 11.0 and OpenBSD 5.4 * A fix allowing aklog to succeed creating native K5 tokens even when = mapping the K5 principal to a K4 one fails * Selected fixes for potential data corruption or client panics under certain conditions For the full list of user visible changes in 1.6.11, please see http://dl.openafs.org/dl/1.6.11 /RELNOTES-1.6.11 Bug reports should be filed to [email protected] . Known issues: 1) With all released versions of OpenAFS, including this one, there is a = risk of database corruption if a database server is shut down and then = brought up again quickly with an altered database. Details are discussed = here: = http://grand.central.org/rt/Ticket/Display.html?id=3D131997&user=3Dguest&p= ass=3Dguest This issue will likely be addressed in the next release. Meanwhile, administrators are advised to make sure that the coordinating server = (the "sync site") has noticed that the peer server is down before the = latter is started again if its local database is modified in any way. This may = take up to 75 seconds. 2) This release contains changes addressing the spurious getcwd() = failures on Linux clients. But it seems these are not yet sufficient at least = for recent kernels, as discussed in the bug report: = http://grand.central.org/rt/Ticket/Display.html?id=3D131780&user=3Dguest&p= ass=3Dguest Stephan Wiesand, 1.6 Branch Release Manager for the OpenAFS Release Team