[linux-lvm] vgchange -ay Killed
Ming Zhang
mingz at ele.uri.edu
Fri Apr 28 16:10:03 UTC 2006
This is what i get when try to active a VG with 3K LVs. repeatable.
LVM version: 2.02.01 (2005-11-23)
Library version: 1.02.02 (2006-01-04)
Driver version: 4.4.0
[root at dualxeon ~]# vgchange -ay
Killed
seem that "Locking memory" only appear once, and then stuck till killed.
--------some debug output if i use vgchang -ay -vvv--------------
Found volume group "vg1"
Getting device info for vg1-v678
dm info
LVM-8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCejSzi1SuM3uO3NWrpDB2Fle5A3Uv6i367 N
[16384]
Locking LV
8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeL0DcqwlzsZSb0p6eIhXnV2uyE8KNAZG2 (R)
Finding volume group for uuid
8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeL0DcqwlzsZSb0p6eIhXnV2uyE8KNAZG2
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
Read vg1 metadata (3001) from /dev/md0 at 272384 size 706783
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
Read vg1 metadata (3001) from /dev/md1 at 272384 size 706783
Found volume group "vg1"
Getting device info for vg1-v679
dm info
LVM-8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeL0DcqwlzsZSb0p6eIhXnV2uyE8KNAZG2 N
[16384]
Locking LV
8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeccjyapQkKwo75je1cFLyZ84RO4LWQnk5 (R)
Finding volume group for uuid
8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeccjyapQkKwo75je1cFLyZ84RO4LWQnk5
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
Read vg1 metadata (3001) from /dev/md0 at 272384 size 706783
/dev/md0: lvm2 label detected
/dev/md1: lvm2 label detected
Read vg1 metadata (3001) from /dev/md1 at 272384 size 706783
Found volume group "vg1"
Getting device info for vg1-v680
dm info
LVM-8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeccjyapQkKwo75je1cFLyZ84RO4LWQnk5 N
[16384]
dm info
8ZZaL55BvKV1b8qj3z60KZBVJOrnHyCeccjyapQkKwo75je1cFLyZ84RO4LWQnk5 N
[16384]
dm info vg1-v680 N [16384]
Locking memory
More information about the linux-lvm
mailing list