This section describes known issues in this update.
The Linux Containers package (lxc) is not available for the i386
architecture.
Running with SELinux enabled on the host can cause issues with Linux Containers. The
workaround is to disable SELinux altogether by setting SELINUX=disabled in
/etc/selinux/config and rebooting the system. Using the
setenforce Permissive command is not sufficient as the
selinuxfs pseudo file system remains mounted. (Bug ID 15967411)
The default location for a container's configuration has changed from
/etc/lxc/ to
name/container/ in namelxc
0.8.0.
To start a container that you created with a previous update of Oracle Linux, specify the -f option to lxc-start, for example:
# lxc-start -n ol6u3 -f /etc/lxc/ol6u3/config
To convert an existing container to use the new location:
Move the container's configuration directory to
/container/:name
# mv /etc/lxc/name /container Edit the /container/
file and change the values of any name/configlxc.rootfs and
lxc.mount parameters to refer to
/container instead of /etc/lxc.
For example, if the config file contained the following
entries:
lxc.rootfs = /etc/lxc/example/rootfs lxc.mount.entry=/lib /etc/lxc/example/rootfs/lib none ro,bind 0 0 lxc.mount.entry=/usr/lib /etc/lxc/example/rootfs/usr/lib none ro,bind 0 0 lxc.mount.entry=/lib64 /etc/lxc/example/rootfs/lib64 none ro,bind 0 0 lxc.mount.entry=/usr/lib64 /etc/lxc/example/rootfs/usr/lib64 none ro,bind 0 0
you would change these entries to read:
lxc.rootfs = /container/example/rootfs lxc.mount.entry=/lib /container/example/rootfs/lib none ro,bind 0 0 lxc.mount.entry=/usr/lib /container/example/rootfs/usr/lib none ro,bind 0 0 lxc.mount.entry=/lib64 /container/example/rootfs/lib64 none ro,bind 0 0 lxc.mount.entry=/usr/lib64 /container/example/rootfs/usr/lib64 none ro,bind 0 0
After converting the container, you do not need to specify the -f option to lxc-start. (Bug ID 15967411)
When using the bnx2x driver in a bridge, disable Transparent Packet
Aggregation (TPA) by including options bnx2x disable_tpa=1 in
/etc/modprobe.conf. (Bug ID 14626070)
Running btrfs filesystem balance converts a non-RAID or concatenated file system setup to RAID-0 after adding a new device. Do not run this command if you do not intend to convert the profile of the file system after adding the new device. (Bug ID 13715389)
Converting an existing ext2, ext3, or
ext4 root file system to btrfs does not carry over the
associated security contexts that are stored as part of a file's extended attributes. With
SELinux enabled and set to enforcing mode, you might experience many permission
denied errors after reboot, and the system might be unbootable. To avoid this
problem, enforce automatic file system relabeling run at bootup time. To trigger automatic
relabeling, create an empty file named autorelabel (for example, by using
touch) in the file system's root directory before rebooting the system
after the initial conversion. The presence of this file instruct SELinux to recreate the
security attributes for all files on the file system. If you forget to do this and rebooting
fails, either temporarily disable SELinux completely by adding selinux=0 to
the kernel boot parameters, or disable enforcing of the SELinux policy by adding
enforcing=0. (Bug ID 13806043)
A failing RAID1 disk might result in a kernel panic with the error kernel: BTRFS
error (device (null)) in btree_writepage_io_failed_hook:3662: IO failure (Error occurred
while writing out btree at offset). (Bug ID 16262571)
The btrfs subvolume get-default command lists all existing subvolumes instead of only the default subvolume. (Bug ID 13815433)
The btrfs filesystem defragment command exits with an exit code of 20 even if it succeeds. (Bug ID 13714531)
Commands such as du might show inconsistent results for file sizes in a btrfs file system when the number of bytes that is under delayed allocation is changing. (Bug ID 13096268)
Btrfs has a limit of 237 hard links to a file. Attempting to create more than this number
of links results in the error Too many links. (Bug ID 16278563)
You might see a message similar to the following during the first reboot of an HP ProLiant server:
[Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)
You can safely ignore this message. The functionality and performance of the operating system and the server are not affected.
The Mellanox ConnectX core, Ethernet, and InfiniBand drivers are supported only for the x86_64 architecture.
(Bug ID 16228063)
A message similar to the following might be recorded in dmesg or
/var/log/messages at boot
time:
udevd (pid): /proc/pid/oom_adj is deprecated, please use /proc/pid/oom_score_adj instead.
The udevd process uses the deprecated oom_adj kernel
interface to prevent it from being killed if the system runs short of memory. You can safely
ignore the message as the action still succeeds. To prevent the message from occurring,
install the package udev-147-2.42.el6.arch.rpm or higher. (Bug ID 13655071,
13712009)
Registering an Oracle Linux guest running under Virtual Box with the Unbreakable Linux
Network (ULN) might fail with a server communication error. The workaround is to run the
following command as root on the
guest:
# echo "uuid=`uuidgen -t`" >> /etc/sysconfig/rhn/up2date
and then run uln_register again. (Bug ID 14696776)
If the xguest package fails to install with a PREIN
script error, enable SELinux by setting SELINUX=enabled in
/etc/selinux/config, reboot the system, and reinstall the
xguest package. (Bug ID 13495388)
If you install an Oracle Linux 6 Update 4 (x86_64) PVHVM guest with either the Desktop or the Software Development Workstation installation options, the X Window System is not accessible after installation when you boot the guest into run level 5. This problem is seen in OVM 3.0 and later.
Use the following workaround:
Boot the guest into run level 3 by appending 3 to the kernel
command line in GRUB, for example:
kernel /vmlinuz-2.6.39-400.15.0.el6uek.x86_64 ... rd_NO_DM 3
After the guest boots, log in as root, and uninstall the
xorg-x11-drv-cirrus package, for example:
# rpm -ev --nodeps xorg-x11-drv-cirrus
You can then either reboot the system into run level 5 or use the init 5 command to switch to run level 5. The X Window System will be accessible on subsequent boots to run level 5. (Bug ID 16280196)
Hardware virtualized with Paravirtualized Drivers (PVHVM) guests on Oracle VM 3.0 crash
during Oracle Database installation if the value of the maximum memory
(maxmem) parameter set for the guest is greater than the amount specified
at boot time (memory). To avoid this issue, ensure that the values of the
maxmem and memory parameters are the same. This issue
has been resolved in Oracle VM 3.1.1. (Bug ID 13396734)
When booting UEK R2 as a 32-bit PVHVM guest, you can safely ignore the kernel message
register_vcpu_info failed: err=-38, which might be displayed. (Bug ID
13713774)
In certain cases, after successfully completing installation and rebooting the system, it is possible for errors such as the following to occur:
Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/meh/handler.py", line 161, in (lambda) File "/usr/lib/anaconda/exception.py", line 44, in handleException File "/usr/lib/python2.6/site-packages/meh/handler.py", line 106, in handleException File "/usr/lib/anaconda/gui.py", line 1169, in mainExceptionWindow ImportError: No module named ui.gui
These errors can safely be ignored.
The upstream release has added support for FCoE target service. This service is not supported with the previous release of the Unbreakable Enterprise Kernel (2.6.32). To use this service, boot your system into the Unbreakable Enterprise Kernel Release 2 (2.6.39) or the Red Hat Compatible Kernel.
Both the mlnx_en and ofa packages contain
mlx4_core. Only one of these packages should be installed. Attempting to
install both packages on a single server results in a package conflict error. If you have a
Mellanox Ethernet Controller, install mlnx_en. If you have a Mellanox
InfiniBand Controller, install ofa. If your system has both controllers,
use ofa as it supports both the Ethernet and InfiniBand controllers.
When configuring the crash kernel for the UEK, only standard crash kernel settings (for
example, crashkernel=128M@32M) are supported. The new settings used by the
Red Hat Compatible Kernel (for example, crashkernel=auto) are not supported
and cause the kdump service to fail to start. (Bug ID 13495212)
If you see the boot-time dmesg error iTCO_wdt: failed to reset
NO_REBOOT flag, device disabled by hardware/BIOS with UEK R2 or iTCO_wdt:
failed to reset NO_REBOOT flag, reboot disabled by hardware with UEK, add the line
blacklist iTCO_wdt to
/etc/modprobe.d/blacklist-watchdog.
The Unbreakable Enterprise Kernel adds support for paravirtualized (PV) drivers in a
hardware virtualized (HVM) guest on Oracle VM. The default is to present only PV drivers when
running in an HVM guest. To run kernel-uek fully hardware virtualized,
including the drivers, add the parameter xen_emul_unplug=never to the boot
parameters in /etc/grub.conf, for example:
kernel /vmlinuz-2.6.32-300.2.1.el6uek ro root=/dev/VolGroup00/LogVol00 xen_emul_unplug=never
Adding this parameter makes the kernel also present the emulated drivers as previously
(for example, the 8139cp network driver).
Selecting all packages in certain groups during installation might not show the correct package count. (Bug ID 11684244)
Oracle Linux 6 defaults to reverse path filtering in strict mode. Some Oracle products and
network storage devices work more reliably with reverse path filtering in loose mode. To
enable loose mode, issue the following command (where iface is the
network interface, for example, eth1).
# sysctl net.ipv4.conf.iface.rp_filter=2The default setting is 1 for strict mode. (Bug ID 10649976)
Certain network operations that utilize receive packet steering could cause errors on the system. (Bug ID 11071685)
If failed paths are restored in a multipath configuration, you might see
udevd-work error messages in /var/log/messages. The
failed paths are restored despite these messages, which you can ignore. (Bug ID
11682171)
The default NFS mount option has changed to NFS v4. To mount an NFS v3 volume (the default in Oracle Linux 5), use the following mount options:
-o vers=3,mountproto=tcp
To set the serial console a hardware-virtualized guest, use following settings in the guest:
Add the following parameters to the kernel boot line in
/etc/grub.conf:
console=tty0 console=ttyS0,57600n8
Add the following line to
/etc/securetty:
ttyS0
On an x86_64 system, if you install the pam.i386 package either
manually or via a package dependency, and the
oracle-rdbms-server-11gR2-preinstall package is also selected, this
overwrites the settings for Oracle Database in /etc/security/limits.conf.
This is most likely to occur during a Kickstart-automated installation that includes
non-standard packages. To restore the settings, run the
oracle-rdbms-server-11gR2-preinstall-verify script. (Bug ID
14212822)
Following the first reboot after installing Oracle Linux 6, you are prompted to register
your system with the Unbreakable Linux Network (ULN). If you did not configure your network
during the installation, the registration process to ULN cannot succeed. To register your
system, log in as root, configure the system's network manually, and run
uln_register.
On some hardware, the console may appear to hang during the boot process after starting
udev. However, the system does boot properly and is accessible. A
workaround to this problem is to add nomodeset as a kernel boot parameter
in /etc/grub.conf. (Bug ID 10094052, 13485328)
For the Unbreakable Enterprise Kernel, deadline is the default I/O
scheduler.
For the Red Hat Compatible Kernel, cfq is the default I/O
scheduler.
For the Unbreakable Enterprise Kernel, the default setting is
kernel.sched_compat_yield=1.
For the Red Hat Compatible Kernel, the default setting is
kernel.sched_compat_yield=0.