Anyone know what kernel / kexec release has the bugfix mentioned in bz
238124 / bz 228685?  I'm trying kernel 2.6.18-36.el5 and kexec
1.101-192.el5 and I'm still seeing issues with cciss devices not getting
mapped properly from /dev/cciss/c0d0p# in the real kernel to something
that the crash kernel understands.  The devices in the crash kernel are
still showing up as /dev/cciss!c0d0# and it's not able to dump properly.
Unfortunately, I don't have access to view bz 228685 so I can't see all
the details there.

        Saving to the local filesystem /dev/cciss/c0d0p3
        e2fsck 1.38 (30-Jun-2005)
        fsck.ext3: while trying to open /dev/cciss/c0d0p3

        The superblock could not be read or does not describe a correct
ext2
        filesystem.  If the device is valid and it really contains an
ext2
        filesystem (and not swap or ufs or something else), then the
superblock
        is corrupt, and you might try running e2fsck with an alternate
superblock:
            e2fsck -b 8193 <device>

        fsck.ext3:
        mount: Mounting /dev/cciss/c0d0p3 on /mnt failed: No such file
or directory
        umount: Couldn't umount /mnt: Invalid argument

Maarten Broekman
Fidelity | Investment Management Technology
Enterprise Platform Services




_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to