Known Issues - Novell SP2 - RELEASE NOTES Release Note

Table of Contents

Advertisement

Chapter 9. Known Issues
• i586 and i686 Machine with more than 16 GB of Memory
Depending on the workload, i586 and i686 machines with 16GB-48GB of memory can run into
instabilities. Machines with more than 48GB of memory are not supported at all. To run on such a
machine, lower the memory with the mem= kernel boot option.
On such memory scenarious we strongly recommend to use a x86-64 with 64-bit SUSE Linux Enterprise
Server and run the x86 applications on it.
• Bootloader and mount by UUID or LABEL
When the way the root device is mounted (by UUID or by label) is changed in YaST, the boot loader
configuration needs to be saved again to make the change effective for the boot loader.
The "mount by" setting displayed in the YaST2 boot loader module is the setting that will be in effect
after saving the configuration.
• EVMS Volumes Might Not Appear When Using iSCSI
If you have installed and configured an iSCSI SAN and have created and configured EVMS Disks or
Volumes on that iSCSI SAN, your EVMS volumes might not be visible or accessible. This problem is
caused by EVMS starting before the iSCSI service. iSCSI must be started and running before any disks
or volumes on the iSCSI SAN can be accessed.
To resolve this problem, enter either chkconfig evms on or chkconfig boot.evms on at the Linux server
console of every server that is part of your iSCSI SAN. This ensures that EVMS and iSCSI start in the
proper order each time your servers reboot.
• cpio and files larger 4GB
cpio is not able to add files larger than 4GB to an archive.
• KDE and IPv6 Support
By default, IPv6 support is not enabled for KDE. You can enable it using the /etc/sysconfig editor of
YaST. This feature is disabled because IPv6 addresses are not properly supported by all Internet service
providers and, as a consequence, would lead to error messages while browsing the Web and delays
while displaying Web pages.
• Installing/Updating on IBM System z9
When installing SUSE Linux Enterprise Server 10 on a System z9, some restrictions apply through
hardware or software. Some of these restrictions are part of these Release Notes. For an updated list,
refer to http://www-128.ibm.com/developerworks/linux/linux390/october2005_restrictions.html.
For IBM System z9 machines ensure to have MCF RJ9967101E or IBM System z9 GA3 base driver
installed. Otherwise Linux reboot will not work.
• Using Disks in z/VM (zSeries)
If SUSE Linux Enterprise Server 10 is installed on disks in z/VM, which reside on the same physical
disk, the created access path (/dev/disk/by-id/) is not unique. The ID of a disk is the ID of the
underlying disk. So if two or more disk are on the same physical disk, they all have the same ID.
19

Advertisement

Table of Contents
loading

This manual is also suitable for:

Suse linux enterprise server 10 service pack 2

Table of Contents