On Mon, Aug 11, 2003 at 02:02:22AM +0200, Terje Kvernes wrote:
> any suggestions are welcome, below is the output from "vgchange -ay
> -vvv" showing the problem.
1) Check kernel message log for any device-mapper errors.
2) Confirm you are using userspace libdevmapper & LVM2 from the
last tarballs we released.
3) If there are no kernel errors and you are using the latest userspace
code, then please log to file (see below, as mentioned in WHATS_NEW) and
send me the log file. [Clear the log file, then run a 'vgscan' followed
by the troublesome 'vgchange -ay'.]
e.g. config file section:
log {
file="/tmp/lvm2.log"
level=7
activation=1
}
Please also send the output of 'lvm version', 'ls -la /dev/mapper' and a
copy of the current volume group backup. (e.g. generate with
'vgcfgbackup').
Alasdair
_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
