[Ocfs-announce] 1.0.13-1 released

[Sunil Mushran]

Mentioned in the README, I think.

It's not any different than upgrading any rpm. The only difference being
the the machine should be rebooted for the newer module to get loaded.

rpm -Uvh <ocfsXX.rpm>
reboot

cat /proc/ocfs/version
will show the version of the module in use.

Ensure that the module is upgraded on all the servers in the cluster.
If upgrading from 1.0.10 or later, rolling upgrade is possible. As in,
one can upgrade one server at a time so that the entire server is not
down at anytime.

If upgrading from older than 1.0.10, a cold upgrade is recommended.

On Mon, 2004-08-23 at 17:28, Arman Rawls wrote:
> Is there anyplace that mentions how to properly upgrade from 1.0.12 to this
> new release?
> 
> Arman
>  
> 
> -----Original Message-----
> From: ocfs-announce-bounces at oss.oracle.com
> [mailto:ocfs-announce-bounces at oss.oracle.com] On Behalf Of Sunil Mushran
> Sent: Friday, August 20, 2004 7:12 PM
> To: ocfs-announce at oss.oracle.com
> Cc: sunil.mushran at oracle.com
> Subject: [Ocfs-announce] 1.0.13-1 released
> 
> All,
> 
> We are pleased to announce the release of OCFS 1.0.13-1. The list of changes
> are listed below.
> 
> For the UnitedLinux/SuSe release, the i686 and IA64 rpms have been built
> with the latest kernel, SP3-241.
> 
> For the Redhat AS2.1 IA64 release, the rpms have been built with the e.43
> kernel. The module will not load on AS2.1 IA64 kernels < e.43.
> 
> For Redhat i686 kernels, Redhat's kernel ABI compatibility will ensure that
> the module loads against all kernels, AS2.1 and EL3.
> 
> Sunil
> 
> ===================================================================
> RELEASE 1.0.13
> 
> There are two changes in this release, both concerning the size of memory
> chunks allocated.
>  
> First concerns the memory block allocated to r/w directories.
> Whereas the older release allocated 128K block of memory, the newer release
> allocs PAGE_SIZE blocks. Whereas the overall size of memory allocated has
> not changed, the number of contiguous pages required for each allocation
> has. In the newer scheme, the 128K is made up of 32 4K pages (on the ia32
> systems). This has been done to take care of the numerous ENOMEMs
> experienced due to lowmem fragmentation on heavily loaded systems.
>  
> The second change concerns the amount of memory allocated to hold the
> lockres hashtable. Now, instead of 32 4K pages, it requires
> 8 4K pages. Once again, this has been done to take care of the ENOMEM error
> one encounters when mounting ocfs volumes on heavily loaded systems.
> ===================================================================
> 
> 
> 
> 
> _______________________________________________
> Ocfs-announce mailing list
> Ocfs-announce at oss.oracle.com
> http://oss.oracle.com/mailman/listinfo/ocfs-announce
>