From: Navindra Umanee <navindra@cs.mcgill.ca>
To: linux-lvm@sistina.com
Subject: [linux-lvm] vgscan goes into an infinite loop (migration issues)
Date: Tue Jan 6 15:59:01 2004 [thread overview]
Message-ID: <20040106165719.A26553@cs.mcgill.ca> (raw)
Hi,
I have an LVM1 system working under 2.4. I've installed 2.6.0 with
devmapper and the LVM2 tools. Now I'm trying to get 2.6.0 to mount my
LVM1 system or at least to convert LVM1 to LVM2.
I have a single IDE harddrive with one VG named /dev/bytepool
containing four LVM partitions. I have a few LVs under
/dev/bytepool/.
vgconvert runs for a long long time, uses more than 3G of memory
(including swap) and then fails with an out of memory error. I can
increase swap if it will help, but I don't think it will.
vgscan does the same thing with global/format set to LVM1. So I put
vgscan in verbose and debug mode:
locking/file_locking.c:158 Locking /var/lock/lvm/V_bytepool RB
toollib.c:305 Finding volume group "bytepool"
device/dev-io.c:325 Opened /dev/hda6
format1/disk-rep.c:353 Found /dev/hda6 in VG bytepool
device/dev-io.c:325 Opened /dev/hda7
format1/disk-rep.c:353 Found /dev/hda7 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda7
device/dev-io.c:325 Opened /dev/hda8
format1/disk-rep.c:353 Found /dev/hda8 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda8
device/dev-io.c:325 Opened /dev/hda9
format1/disk-rep.c:353 Found /dev/hda9 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda9
format1/disk-rep.c:353 Found /dev/hda6 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda6
format1/disk-rep.c:353 Found /dev/hda7 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda7
format1/disk-rep.c:353 Found /dev/hda8 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda8
format1/disk-rep.c:353 Found /dev/hda9 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda9
format1/disk-rep.c:353 Found /dev/hda6 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda6
format1/disk-rep.c:353 Found /dev/hda7 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda7
format1/disk-rep.c:353 Found /dev/hda8 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda8
format1/disk-rep.c:353 Found /dev/hda9 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda9
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda6
format1/disk-rep.c:353 Found /dev/hda7 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda7
format1/disk-rep.c:353 Found /dev/hda8 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda8
format1/disk-rep.c:353 Found /dev/hda9 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda9
format1/disk-rep.c:353 Found /dev/hda6 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda6
format1/disk-rep.c:353 Found /dev/hda7 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda7
format1/disk-rep.c:353 Found /dev/hda8 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda8
format1/disk-rep.c:353 Found /dev/hda9 in VG bytepool
format1/disk-rep.c:392 Ignoring duplicate PV on /dev/hda9
[...]
Basically it's an infinite loop. Any idea what is going on? I would
greatly appreciate any suggestions.
Btw, it was quite an unpleasant shock to find that Linux 2.6.0 no
longer supported my LVM filesystems -- the kernel documentation
completely fails to mention anything at all about LVM changes. Can
someone take care of this oversight?
I *am* really glad my partitions and data have not been toasted so
far... :-)
Thanks,
Navin.
next reply other threads:[~2004-01-06 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 15:59 Navindra Umanee [this message]
2004-01-06 17:00 ` [linux-lvm] vgscan goes into an infinite loop (migration issues) Alasdair G Kergon
2004-01-06 17:15 ` Navindra Umanee
2004-01-06 17:30 ` Alasdair G Kergon
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=20040106165719.A26553@cs.mcgill.ca \
--to=navindra@cs.mcgill.ca \
--cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.