[OpenAFS] Re: [OpenAFS-announce] OpenAFS 1.5.28 released. Production Version for Windows. Please test Demand Attach File Server.
Derrick Brashear
shadow@gmail.com
Mon, 10 Dec 2007 15:56:47 -0500
------=_Part_21049_26709350.1197320207488
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
On Dec 10, 2007 3:49 PM, Jason Edgecombe <jason@rampaginggeek.com> wrote:
> Jeffrey Altman wrote:
> > 1.5.28 is the recommended production ready release of OpenAFS for
> > Microsoft Windows users. It supports all Microsoft Windows operating
> > systems from Windows 2000 through Windows Vista including both 32-bit
> > and 64-bit architectures. The 1.5.28 release continues the recent
> > efforts at optimizing the performance of the Windows client and
> > improving its scalability.
> >
> > For UNIX, Linux, and MacOS X the recommend production ready release of
> > OpenAFS is 1.4.5. The 1.5.28 Windows client is fully compatible with
> > all AFS server versions.
> >
> > Please visit http://www.openafs.org/windows.html for up to date
> > information on the status of the OpenAFS for Windows client.
> >
> > For Microsoft Windows:
> >
> > This release fixes reported bugs:
> >
> > * In 1.5.21 the Windows client began notifying the file server
> > during suspend and shutdown operations by calling the
> > GiveUpAllCallBacks RPC. It was discovered that all file server
> > releases prior to 1.4.6 (not yet released) and 1.5.28 do not
> > safely implement the RPC and can crash as a result. Therefore,
> > in 1.5.28 calling the GiveUpAllCallBacks has been disabled by
> > default. This call will be re-enabled in a future release in
> > approximately six months. Organizations should prepare to upgrade
> > their file servers to 1.4.6 when it is released.
> >
> > * Optimizations in the handling of .readonly volume callback
> > expirations were added. (a) The most recent callback expiration
> > is applied to all objects from the same .readonly volume.
> > (b) An optional automatic renewal can be activated by setting
> > the 'daemonCheckVolCBInterval' to a non-zero number of seconds.
> >
> > * Previous versions of the Windows client only supported
> > 32-bit data version values. As of 1.5.28 64-bit data versions
> > are supported.
> >
> > * aklog and asetkey no longer generate an exception if Kerberos
> > for Windows is not installed.
> >
> > * If the Microsoft LSA authentication function calls report a
> > temporary out of memory condition, fail the current authentication
> > attempt and do not panic.
> >
> > * When the AFS client service is shutting down, prevent the
> > daemon check thread from executing which may access discarded
> > lock objects or unmapped memory.
> >
> > * NEW FEATURE: New service parameter registry value "FollowBackupPath"
> > This provides equivalent functionality to the UNIX afsd -backuptree
> > option. When set to a non-zero value, normal mount points
> > originating in a .backup volume will prefer a .backup volume.
> >
> > * MSI installer now installs afslogon.dll and afscpcc.exe within
> > ...\OpenAFS\Client\Program\. This avoids confusion when installing
> > on 64-bit Windows.
> >
> > MIT Kerberos for Windows 3.2.2
> > The recommended version of Kerberos for Windows to use with
> > OpenAFS is version 3.2.2. KFW can be downloaded from MIT or
> > Secure Endpoints. 64-bit Windows installers for KFW are only
> > available from Secure Endpoints.
> > http://www.secure-endpoints.com/index.html#kfw
> >
> > Known issues in the Windows client:
> > . Beta versions of the Network Identity Manager AFS plug-in must
> > be uninstalled prior to the installation of OpenAFS 1.5.26
> > . Windows Vista does not support the WinHelp file format used
> > by afscreds.exe and afs_control.exe. A download is available
> > from Microsoft.
> > . On Windows Vista, afscreds.exe is not User Account Control (UAC)
> > compatible and must be "Run as Administrator" in order to
> > start/stop the AFS client service.
> >
> > Significant changes since 1.5.27 for all platforms:
> >
> > * An issue which could cause erroneous data to be written to the
> > CacheItems file on disk on multi-CPU systems has been corrected.
> >
> > * Several fileserver bugs fixed.
> >
> > AIX:
> >
> > * aklog no longer triggers a terminal hangup on AIX 5 (aklog NAS module
> > is similarly updated).
> >
> > * Kernel AFSDB support corrected.
> >
> > Linux:
> >
> > * NFS translator authenticated write bug fixed.
> >
> > * Hash inodes to avoid mmap hangs.
> >
> > * Updates for newer kernels.
> >
> > The Demand Attach File Server is a compile time option that produces a
> > file server that supports several new and important features:
> >
> > * an enhanced volume management library that supports:
> > . lock-less I/O
> > . on-demand attachment of volumes
> > . parallel shutdown of the file server
> > . on-line salvaging of volumes
> > . automatic detachment of inactive volumes
> >
> > * a new salvageserver daemon which can salvage volumes on-demand
> >
> > * a modified bos and bosserver
> > . fileserver state saving and restoration
> > - host state
> > - callback state
> >
> > With the DAFS, shutdown and startup of the file server is significantly
> > faster. Instead of salvaging a partition at a time, individual volumes
> > are salvaged in the background while volumes that do not need salvaging
> > are served by the fileserver to clients. Volumes are attached on-demand
> > and detached when no longer required. This reduces the number of
> > volumes that may require salvaging upon a restart.
> >
> > The DAFS requires significant testing before it can be put into a
> > production release. If your organization is willing to assist the
> > gatekeepers with testing this functionality, please contact us at
> > gatekeepers@openafs.org.
> >
> >
> > Please send reports of successful deployments to
> > openafs-info@openafs.org and report problems to openafs-bugs@openafs.org
> .
> >
> > Jeffrey Altman
> > for the OpenAFS Gatekeepers
> >
> >
> >
> I seem to recall that there was a bug in which you could not move a
> volume from a 1.5 server to 1.4 server.
>
> Is that correct? If so, was the bug fixed in 1.5.28?
>
someone said they had a problem moving volumes 1.5->1.4, but there's no open
bug about it.
------=_Part_21049_26709350.1197320207488
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<br><br><div class="gmail_quote">On Dec 10, 2007 3:49 PM, Jason Edgecombe <<a href="mailto:jason@rampaginggeek.com">jason@rampaginggeek.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">Jeffrey Altman wrote:<br>> 1.5.28 is the recommended production ready release of OpenAFS for<br>> Microsoft Windows users. It supports all Microsoft Windows operating<br>> systems from Windows 2000 through Windows Vista including both 32-bit
<br>> and 64-bit architectures. The 1.5.28 release continues the recent<br>> efforts at optimizing the performance of the Windows client and<br>> improving its scalability.<br>><br>> For UNIX, Linux, and MacOS X the recommend production ready release of
<br>> OpenAFS is 1.4.5. The 1.5.28 Windows client is fully compatible with<br>> all AFS server versions.<br>><br>> Please visit <a href="http://www.openafs.org/windows.html" target="_blank">http://www.openafs.org/windows.html
</a> for up to date<br>> information on the status of the OpenAFS for Windows client.<br>><br>> For Microsoft Windows:<br>><br>> This release fixes reported bugs:<br>><br>> * In 1.5.21 the Windows client began notifying the file server
<br>> during suspend and shutdown operations by calling the<br>> GiveUpAllCallBacks RPC. It was discovered that all file server<br>> releases prior to 1.4.6 (not yet released) and 1.5.28 do not<br>> safely implement the RPC and can crash as a result. Therefore,
<br>> in 1.5.28 calling the GiveUpAllCallBacks has been disabled by<br>> default. This call will be re-enabled in a future release in<br>> approximately six months. Organizations should prepare to upgrade
<br>> their file servers to 1.4.6 when it is released.<br>><br>> * Optimizations in the handling of .readonly volume callback<br>> expirations were added. (a) The most recent callback expiration<br>> is applied to all objects from the same .readonly volume.
<br>> (b) An optional automatic renewal can be activated by setting<br>> the 'daemonCheckVolCBInterval' to a non-zero number of seconds.<br>><br>> * Previous versions of the Windows client only supported
<br>> 32-bit data version values. As of 1.5.28 64-bit data versions<br>> are supported.<br>><br>> * aklog and asetkey no longer generate an exception if Kerberos<br>> for Windows is not installed.
<br>><br>> * If the Microsoft LSA authentication function calls report a<br>> temporary out of memory condition, fail the current authentication<br>> attempt and do not panic.<br>><br>> * When the AFS client service is shutting down, prevent the
<br>> daemon check thread from executing which may access discarded<br>> lock objects or unmapped memory.<br>><br>> * NEW FEATURE: New service parameter registry value "FollowBackupPath"<br>> This provides equivalent functionality to the UNIX afsd -backuptree
<br>> option. When set to a non-zero value, normal mount points<br>> originating in a .backup volume will prefer a .backup volume.<br>><br>> * MSI installer now installs afslogon.dll and afscpcc.exe within
<br>> ...\OpenAFS\Client\Program\. This avoids confusion when installing<br>> on 64-bit Windows.<br>><br>> MIT Kerberos for Windows 3.2.2<br>> The recommended version of Kerberos for Windows to use with
<br>> OpenAFS is version 3.2.2. KFW can be downloaded from MIT or<br>> Secure Endpoints. 64-bit Windows installers for KFW are only<br>> available from Secure Endpoints.<br>> <a href="http://www.secure-endpoints.com/index.html#kfw" target="_blank">
http://www.secure-endpoints.com/index.html#kfw</a><br>><br>> Known issues in the Windows client:<br>> . Beta versions of the Network Identity Manager AFS plug-in must<br>> be uninstalled prior to the installation of OpenAFS
1.5.26<br>> . Windows Vista does not support the WinHelp file format used<br>> by afscreds.exe and afs_control.exe. A download is available<br>> from Microsoft.<br>> . On Windows Vista, afscreds.exe
is not User Account Control (UAC)<br>> compatible and must be "Run as Administrator" in order to<br>> start/stop the AFS client service.<br>><br>> Significant changes since 1.5.27 for all platforms:
<br>><br>> * An issue which could cause erroneous data to be written to the<br>> CacheItems file on disk on multi-CPU systems has been corrected.<br>><br>> * Several fileserver bugs fixed.<br>><br>> AIX:
<br>><br>> * aklog no longer triggers a terminal hangup on AIX 5 (aklog NAS module<br>> is similarly updated).<br>><br>> * Kernel AFSDB support corrected.<br>><br>> Linux:<br>><br>> * NFS translator authenticated write bug fixed.
<br>><br>> * Hash inodes to avoid mmap hangs.<br>><br>> * Updates for newer kernels.<br>><br>> The Demand Attach File Server is a compile time option that produces a<br>> file server that supports several new and important features:
<br>><br>> * an enhanced volume management library that supports:<br>> . lock-less I/O<br>> . on-demand attachment of volumes<br>> . parallel shutdown of the file server<br>> . on-line salvaging of volumes
<br>> . automatic detachment of inactive volumes<br>><br>> * a new salvageserver daemon which can salvage volumes on-demand<br>><br>> * a modified bos and bosserver<br>> . fileserver state saving and restoration
<br>> - host state<br>> - callback state<br>><br>> With the DAFS, shutdown and startup of the file server is significantly<br>> faster. Instead of salvaging a partition at a time, individual volumes
<br>> are salvaged in the background while volumes that do not need salvaging<br>> are served by the fileserver to clients. Volumes are attached on-demand<br>> and detached when no longer required. This reduces the number of
<br>> volumes that may require salvaging upon a restart.<br>><br>> The DAFS requires significant testing before it can be put into a<br>> production release. If your organization is willing to assist the<br>> gatekeepers with testing this functionality, please contact us at
<br>> <a href="mailto:gatekeepers@openafs.org">gatekeepers@openafs.org</a>.<br>><br>><br>> Please send reports of successful deployments to<br>> <a href="mailto:openafs-info@openafs.org">openafs-info@openafs.org
</a> and report problems to <a href="mailto:openafs-bugs@openafs.org">openafs-bugs@openafs.org</a>.<br>><br>> Jeffrey Altman<br>> for the OpenAFS Gatekeepers<br>><br>><br>><br></div></div>I seem to recall that there was a bug in which you could not move a
<br>volume from a 1.5 server to 1.4 server.<br><br>Is that correct? If so, was the bug fixed in 1.5.28?<br></blockquote><div><br>someone said they had a problem moving volumes 1.5->1.4, but there's no open bug about it.
<br> <br></div></div><br>
------=_Part_21049_26709350.1197320207488--