Hi,
I encounter the same problem as described in an old thread.
In my case I use the cobbler integrated in Redhat Satellite and what to use the keep_rhn_host_keys snippet. I found that a got always a kernel panic when a mount is done on an lvm or swap partition.
E.g. the previous installation has following partition layout: # fdisk -l /dev/cciss/c0d0
Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes 255 heads, 63 sectors/track, 53535 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 * 1 25 200781 83 Linux /dev/cciss/c0d0p2 26 53535 429819075 8e Linux LVM
If you create a small snippet with following content: mkdir /tmp/aaaaa mount /dev/cciss/c0d0p2 /tmp/aaaaa
The mount fails as expected but after the new partitions are created and formatted the kernel panic occurs.
Does anybody encounter the same problem?
Thanks Jürgen
On 8 March 2011 20:05, Jürgen Schilp juergen.schilp@alice-dsl.net wrote:
Hi,
I encounter the same problem as described in an old thread.
In my case I use the cobbler integrated in Redhat Satellite and what to use the keep_rhn_host_keys snippet. I found that a got always a kernel panic when a mount is done on an lvm or swap partition.
E.g. the previous installation has following partition layout: # fdisk -l /dev/cciss/c0d0
Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes 255 heads, 63 sectors/track, 53535 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 * 1 25 200781 83 Linux /dev/cciss/c0d0p2 26 53535 429819075 8e Linux LVM
If you create a small snippet with following content: mkdir /tmp/aaaaa mount /dev/cciss/c0d0p2 /tmp/aaaaa
The mount fails as expected but after the new partitions are created and formatted the kernel panic occurs.
Does anybody encounter the same problem?
I still see this with Centos 5.5 installs (also with a P800 RAID controller). I think it's a bug with the kernel shipped with that version of RH/Centos. However, happily, the problem isn't present with Scientific Linux 6.
I tried it also with RHEL5.4 and 5.6 and no kernel panic occurs. The problem occurs only with 5.5
I found a nice workaround. Before the snippet runs I unload the ext4 kernel module and then no kernel panic occurs.
I forwarded the problem to Redhat.
On 08.03.2011 22:36, Jonathan Underwood wrote:
On 8 March 2011 20:05, Jürgen Schilpjuergen.schilp@alice-dsl.net wrote:
Hi,
I encounter the same problem as described in an old thread.
In my case I use the cobbler integrated in Redhat Satellite and what to use the keep_rhn_host_keys snippet. I found that a got always a kernel panic when a mount is done on an lvm or swap partition.
E.g. the previous installation has following partition layout: # fdisk -l /dev/cciss/c0d0
Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes 255 heads, 63 sectors/track, 53535 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 25 200781 83 Linux /dev/cciss/c0d0p2 26 53535 429819075 8e Linux LVM
If you create a small snippet with following content: mkdir /tmp/aaaaa mount /dev/cciss/c0d0p2 /tmp/aaaaa
The mount fails as expected but after the new partitions are created and formatted the kernel panic occurs.
Does anybody encounter the same problem?
I still see this with Centos 5.5 installs (also with a P800 RAID controller). I think it's a bug with the kernel shipped with that version of RH/Centos. However, happily, the problem isn't present with Scientific Linux 6. _______________________________________________ cobbler-devel mailing list cobbler-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/cobbler-devel
On Tue, 08 Mar 2011 21:05:17 +0100, Jürgen Schilp juergen.schilp@alice-dsl.net wrote:
Hi,
I encounter the same problem as described in an old thread.
In my case I use the cobbler integrated in Redhat Satellite and what to use the keep_rhn_host_keys snippet. I found that a got always a kernel panic when a mount is done on an lvm or swap partition.
E.g. the previous installation has following partition layout: # fdisk -l /dev/cciss/c0d0
Disk /dev/cciss/c0d0: 440.3 GB, 440345714688 bytes 255 heads, 63 sectors/track, 53535 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 25 200781 83 Linux /dev/cciss/c0d0p2 26 53535 429819075 8e Linux LVM
If you create a small snippet with following content: mkdir /tmp/aaaaa mount /dev/cciss/c0d0p2 /tmp/aaaaa
The mount fails as expected but after the new partitions are created and formatted the kernel panic occurs.
Does anybody encounter the same problem?
Sounds like a bug where the OS fails to read the partition table again. I'd file a bug with Red Hat on it. I doubt we can do anything about this other than to say not to use that snippet, which is less than optimum.
I might check scsi-rescan from rhel6 and try doing what it does. That might get the kernel to reevaluate its environment and not panic. I'd do it after the keep_rhn_host_keys snippet runs.
cobbler-devel@lists.fedorahosted.org