A.1 January 2014 (OES 11 SP2)

A.1.1 Clustering LVM Volume Groups with Novell Cluster Services

Location

Change

Section 8.3.2, Creating an LVM Volume Group Cluster Resource with NSSMU

Section 8.3.3, Creating an LVM Volume Group Cluster Resource with NLVM Commands

If you enable NCP for the volume, the LVM volume name must comply with the limitations for NCP volume names described in Section 5.4, Naming Conventions for NCP Volume Names. If you use lowercase letters for the volume name, they are automatically changed to uppercase for the NCP volume name.

You can specify an unshared initialized device, a shared device with no data partitions, or an uninitialized device.

Section 8.11, Deleting a Clustered LVM Volume (Created in NSSMU or NLVM)

This section is new.

A.1.2 Managing Linux Volumes with NLVM Commands

Location

Change

Section 7.7, Creating a Non-LVM Linux Volume

Section 7.8, Creating an LVM Logical Volume

If you enable NCP for the volume, the volume name must comply with the limitations for NCP volume names described in Section 5.4, Naming Conventions for NCP Volume Names. If you use lowercase letters for the volume name, they are automatically changed to uppercase for the NCP volume name.

Section 7.10, Mounting Linux Volumes

The nlvm linux mount command allows you to mount a Linux volume in Linux and NCP with a single command.

Section 7.11, Dismounting Linux Volumes

The nlvm linux unmount command allows you to dismount a Linux volume from NCP and Linux with a single command.

A.1.3 Managing Linux Volumes with NSSMU

Location

Change

Section 6.9, Creating a Non-LVM Linux Volume

Section 6.10, Creating an LVM Logical Volume

If you enable NCP for the volume, the volume name must comply with the limitations for NCP volume names described in Section 5.4, Naming Conventions for NCP Volume Names. If you use lowercase letters for the volume name, they are automatically changed to uppercase for the NCP volume name.

Section 6.12, Mounting a Linux Volume

This section is new.

Section 6.13, Dismounting a Linux Volume

This section is new.

A.1.4 Overview of Linux POSIX File Systems

Location

Change

Default Ext3 Inode Size

To allow space for extended attributes and ACLs for a file on Ext3 file systems, the default inode size for Ext3 was increased from 128 bytes on SLES 10 to 256 bytes on SLES 11.

A.1.5 Planning for Linux POSIX Volumes

Location

Change

Section 5.2, Using RAID Devices for Linux POSIX Volumes

We recommend that you do not use Linux software RAIDs (such as MD RAIDs and Device Mapper RAIDs) for devices that you plan to use for storage objects that are managed by NSS management tools. The Novell Linux Volume Manager (NLVM) utility and the NSS Management Utility (NSSMU) list Linux software RAID devices that you have created by using Linux tools. Beginning with Linux Kernel 3.0 in OES 11 SP1, NLVM and NSSMU can see these devices, initialize them, and allow you to create storage objects on them. However, this capability has not yet been fully tested.

IMPORTANT:In OES 11, a server hang or crash can occur if you attempt to use a Linux software RAID when you create storage objects that are managed by NSS management tools.

A.1.6 What’s New or Changed for Linux POSIX Volumes

Location

Change

Section 2.2, What’s New (OES 11 SP2)

This section is new.