Red Hat Bugzilla – Bug 157669
attempt to access beyond end of device: ext2 symlink/EA problem
Last modified: 2007-11-30 17:07:07 EST
+++ This bug was initially created as a clone of Bug #157570 +++ * RHEL3 U5 s390-AS & s390x-AS * test tree RHEL3-U5-re0512.0 * trying to ipl install images when ipl-ing the installer, there are errors that indicate problems with the initrd: > RAMDISK: Compressed image found at block 0 > Freeing initrd memory: 5779k freed > VFS: Mounted root (ext2 filesystem) readonly. > Freeing unused kernel memory: 40k freed > attempt to access beyond end of device > 01:00: rw=0, want=1815031343, limit=40000 > attempt to access beyond end of device > 01:00: rw=0, want=1815031343, limit=40000 > attempt to access beyond end of device > 01:00: rw=0, want=1852400244, limit=40000 > attempt to access beyond end of device > 01:00: rw=0, want=1852400244, limit=40000 > attempt to access beyond end of device > 01:00: rw=0, want=1852400244, limit=40000 > Kernel panic: No init found. Try passing init= option to kernel. > 00: HCPGSP2629I The virtual machine is placed in CP mode due to a SIGP stop from > CPU 01. > 01: HCPGIR450W CP entered; disabled wait PSW 00020001 80000000 00000000 000112E0
This is the ext2 variant of a known ext3 compatibility problem. If you create a symlink with an SELinux label, using a 2.6 kernel, then older 2.4 kernels will not be able to follow the symlinks properly. I've already fixed it in upstream 2.4; I'll attach the patch for RHEL-3 once I've built and tested it.
Removing dependency on closed distro bug 157570.
Created attachment 114872 [details] Compatibility fix for symlinks with EAs on ext2
A fix for this problem has just been committed to the RHEL3 U6 patch pool this evening (in kernel version 2.4.21-32.6.EL).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-663.html