From: Ming Zhang <mingz@ele.uri.edu>
To: linux-lvm <linux-lvm@redhat.com>
Subject: [linux-lvm] vgchange -ay Killed
Date: Fri, 28 Apr 2006 12:10:03 -0400 [thread overview]
Message-ID: <1146240603.23548.106.camel@localhost.localdomain> (raw)
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
next reply other threads:[~2006-04-28 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 16:10 Ming Zhang [this message]
2006-04-28 22:09 ` [linux-lvm] vgchange -ay Killed Jonathan E Brassow
2006-04-28 22:10 ` Ming Zhang
2006-04-29 16:30 ` Barnaby Claydon
2006-04-29 22:24 ` Alasdair G Kergon
2006-04-29 22:58 ` Ming Zhang
[not found] ` <e651e1f7ae134a3bddcd370a7e29119d@redhat.com>
[not found] ` <1146323005.15799.8.camel@localhost.localdomain>
2006-04-29 21:56 ` Ming Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1146240603.23548.106.camel@localhost.localdomain \
--to=mingz@ele.uri.edu \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).