From: Tupshin Harper <tupshin@tupshin.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] weird duplicate pv problem
Date: Wed Dec 17 17:25:02 2003 [thread overview]
Message-ID: <3FE0E57A.9010509@tupshin.com> (raw)
In-Reply-To: <3FE0C0CA.6050400@tupshin.com>
Tupshin Harper wrote:
> I have an lvm2 volume group composed of about 8 different pvs.
> Recently, most lvm commmands started displaying errors like below. Not
> that it is claiming duplicate PVs, but the duplicates are contained in
> /dev/nbd/*, and I'm not actually using any network block devices. I
> have NBD comiled into the kernel, and I'm about to compiling a kernel
> with nbd not compiled in and see if that helps, but it seems extremely
> odd that lvm would detect duplicate pvs on unused nbd devices.
>
> The effects of the problem (in addition to getting these warnings, are
> that any change to a lv(resizing, for example), will render that lv
> inactive or suspended (have seen both), until I do a magic incarnation
> that involves first "vgcfgrestore" and then "lvchange -a y" on the
> affected lv. Note that vgcfgrestore does not make the warnings go
> away, but it does allow the lvchange command to succeed.
>
> Any thoughts? FWIW, I am using devfs, and I'm still curious about a
> reasonable migration strategy to move an lvm2 setup to non-devfs.
> Kernel 2.6.0-test11, lvm tools that come with debian sid(lvm version
> 2.00.05, library version 1.00.05-ioctl-cvs, driver version 4.0.0).
>
> -Tupshin
>
As I suspected, running a kernel with nbd compiled as a module and not
loading it at startup avoids this probem. But this doesn't bring me any
closer to an understanding of why lvm would see duplicate pv id's on nbd
devices that I never used.
-Tupshin
prev parent reply other threads:[~2003-12-17 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 14:48 [linux-lvm] weird duplicate pv problem Tupshin Harper
2003-12-17 17:25 ` Tupshin Harper [this message]
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=3FE0E57A.9010509@tupshin.com \
--to=tupshin@tupshin.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox