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
