From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [linux-lvm] vgchange -ay Killed From: Ming Zhang In-Reply-To: <01309aa0302de7b36b75ce2612b38706@redhat.com> References: <1146240603.23548.106.camel@localhost.localdomain> <01309aa0302de7b36b75ce2612b38706@redhat.com> Date: Fri, 28 Apr 2006 18:10:41 -0400 Message-Id: <1146262242.23548.207.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: mingz@ele.uri.edu, LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" To: Jonathan E Brassow Cc: LVM general discussion and development 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/ > > >