[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [linux-lvm] vgchange -ay Killed



Have you tried creating less than 3,000 LVs at a time? Maybe start with 1,000 and make sure it activates, then maybe 2,000 and test again - until you find the threshold where it breaks?

Not that I'm an expert on data storage, but if you need 3,000 LVs, then you should probably be using more than 1 VG...

-Barnaby



Ming Zhang wrote:
no. i do
lvcreate -L1G -nlv1 vg1
...
lvcreate -L1G -nlv3000 vg1

so total 3000 logical volumes.

then optionally i do lvscan, vgscan, pvscan. all kinds of scan. seems
not fast.

then i reboot, and then the vg will fail to activate all lv.

ming


On Fri, 2006-04-28 at 17:09 -0500, Jonathan E Brassow wrote:
You mean:
1) lvcreate -L 3k -n lv vg
2) vgchange -an vg
3) vgchange -ay vg

or do you mean something else?

  brassow

On Apr 28, 2006, at 11:10 AM, Ming Zhang wrote:

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


_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


_______________________________________________
linux-lvm mailing list
linux-lvm redhat com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]