I just checked my own RHEL5 systems (which haven't been able to dump crashes for different reasons until 5.2), and crashlv works fine...because it's the longest volume name so it's the one only 1 space between the LV and VG names.
Just out of curiosity, what does your kdump.conf look like? Are you referring to your crash LV as /dev/mapper/rootvg-crashlv or /dev/rootvg/crashlv? Maarten Broekman Email: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jan Frode Myklebust Sent: Thursday, July 31, 2008 3:20 AM To: [email protected] Subject: [rhelv5-list] Re: RHEL6 Wishlist -- Less Regressions, more QA On 2008-07-26, Paolo Campegiani <[EMAIL PROTECTED]> wrote: >> Wow! I thought I was the only one seeing such long times to resolve >> support issues. > > It takes one year to fix this bug: > https://bugzilla.redhat.com/show_bug.cgi?id=250419 Similarly I'm still waiting for RHEL5 to fix this bug https://bugzilla.redhat.com/show_bug.cgi?id=360111 (Also reported as a RHEL service request about the same time.) Reported with proposed fix in october last year, will hopefully be included in 5.3. It's such a trivial bug/fix, and very annoying having to manually fix on my systems for a year before it's fixed in RHEL. Patch was to use awk to print argument number, instead of counting spaces (!): - emit " VGRP=\`lvm lvs | grep \$i | cut -d\" \" -f4\`" + emit " VGRP=\`lvm lvs | grep \$i | awk '{ print \$2 }'\`" without the patch "crash" wount work on non-default volume names, and will just stop at the crash shell after a crash :( -jf _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
