Thanks for the info. Does this also mean that kdump isn't able to read /proc/vmcore off of them (cciss partitions) when it's trying to dump? I ask because I changed from writing to a filesystem to scp'ing to a remote system as a trusted user and dumping there. Since I made that change I've only managed to get "Kernel panic - not syncing: Fatal exception" errors after a stack trace which includes :cciss: calls (:cciss:cciss_getgeometry, :cciss:cciss_init_one, and :cciss:sendcmd).
Maarten Broekman -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jarod Wilson Sent: Wednesday, August 29, 2007 2:06 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] Help needed with kdump on cciss devices Broekman, Maarten wrote: > I'm currently trying to get RHEL5 kdump to work with my cciss-based > internal drives. Every time I point kdump at my /var/crash partition > (ext3 /dev/cciss/c0d0p5), kdump complains that the filesystem isn't > ext2. Anyone had luck getting this to work? Both cciss and cpqarray controllers do things a little different than the norm w/their partitions, which throws the rhel5 kdump for a bit of a loop when your try to specify a specific partition. We've got this fixed properly for rhel5.1. -- Jarod Wilson [EMAIL PROTECTED] _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
