Correct.  With the awk patch, both /dev/VG/LV and /dev/mapper/VG-LV will
work.  Without the awk patch, only /dev/VG/LV will work since
/dev/mapper/VG-LV are just links to /dev/VG/LV.  Later in the init
script, it checks the DUMPDEV which is /dev/mapper/VG-LV on your system.
Since the link wasn't correctly made because of the use of cut instead
of awk, that DUMPDEV doesn't exist.

The use of awk is definitely far more appropriate.  I was just noting
that kdump would work fine with /dev/VG/LV as the dump device instead of
/dev/mapper/VG-LV.

Maarten Broekman
Email: [EMAIL PROTECTED]


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jan Frode Myklebust
Sent: Friday, August 01, 2008 2:48 AM
To: [email protected]
Subject: [rhelv5-list] Re: RHEL6 Wishlist -- Less Regressions, more QA

On 2008-07-31, Broekman, Maarten <[EMAIL PROTECTED]> wrote:
> 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.

It's counting the total number of spaces before volume group name:

         emit "   VGRP=\`lvm lvs | grep \$i | cut -d\" \" -f4\`"

So spaces both before and after LV name is counted. This is my
vg and lvs:

-------------------------------
$ sudo lvm lvs
  LV       VG     Attr   LSize  Origin Snap%  Move Log Copy% 
  crashlv  rootvg -wi-ao  8.00G                              
  locallv  rootvg -wi-ao  1.00G                              
  projects rootvg -wi-ao 20.00G                           
  rootlv   rootvg -wi-ao  5.00G                              
  swaplv   rootvg -wi-ao  2.00G                              
  varlv    rootvg -wi-ao  3.00G                              
-------------------------------

And here the kdump script would only be able to find the VG name for
"projects", and I think it was trying to mount /dev/mapper/-crashlv (or
one of the other lv's) when it failed.

----------------------------------------------
$ sudo lvm lvs | cut -d" " -f4




rootvg



----------------------------------------------

>
> 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?

-------------------------------
$ grep -v ^# /etc/kdump.conf
ext3 /dev/mapper/rootvg-crashlv
path /
default reboot
-------------------------------

This works fine with the mkdumprd patched to use awk instead of sed.

     -    emit "   VGRP=\`lvm lvs | grep \$i | cut -d\" \" -f4\`"
     +    emit "   VGRP=\`lvm lvs | grep \$i | awk '{ print \$2 }'\`"



  -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

Reply via email to