Bugzilla Bug 156009

I recently stumbled onto a problem where I had typoed my lvm.conf in the
chroot. When booting the machine I found out that genkernel happily used my
typoed lvm.conf in the initrd. You can use lvm dumpconfig to detect if lvm.conf
is valid.

rj ~ # lvm dumpconfig
  Parse error at line 79: expected a value
  Failed to load config file /etc/lvm/lvm.conf
rj ~ # echo $?
255
rj ~ # lvm dumpconfig
devices {
        dir="/dev"
        scan="/dev"
        filter="r|/dev/cdrom|"
        cache="/etc/lvm/.cache"
        write_cache_state=1
        sysfs_scan=1
        md_component_detection=1
}
activation {
        missing_stripe_filler="/dev/ioerror"
        reserved_stack=256
        reserved_memory=8192
        process_priority=-18
        mirror_region_size=512
        mirror_log_fault_policy="allocate"
        mirror_device_fault_policy="remove"
}
global {
        umask=63
        test=0
        activation=1
        proc="/proc"
        locking_type=1
        locking_dir="/var/lock/lvm"
}
shell {
        history_size=100
}
backup {
        backup=1
        backup_dir="/etc/lvm/backup"
        archive=1
        archive_dir="/etc/lvm/archive"
        retain_min=10
        retain_days=30
}
log {
        verbose=0
        syslog=1
        overwrite=0
        level=0
        indent=1
        command_names=0
        prefix="  "
}
rj ~ # echo $?
0

Ehh... ok... got a patch?

OK, I think I've fixed this in subversion/3.4.7_pre5

This is fixed in genkernel 3.4.7 which is now in the tree.