From: Timshel Knoll <timshel@pobox.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] Re: pvmove failure ...
Date: Sat, 9 Jun 2001 11:13:03 +1000 [thread overview]
Message-ID: <20010609111303.A30742@knoll.ln> (raw)
In-Reply-To: <20010609104822.B29022@knoll.ln>
[please CC all replies to me, I don't read mail from this list]
On Sat, Jun 09, 2001 at 10:48:22AM +1000, Timshel Knoll wrote:
> [please CC all replies to me, I don't read mail from this list]
>
> > The ENXIO error is returned if the vg you are trying to move does not
> > exist (at least that's what it looks like). This is returned from
> > within the kernel when vg_ptr = NULL inside lvm_do_pe_lock_unlock().
> >
> > It would _appear_ that /dev/vg0/group is pointing to a bogus device.
> > In lvm_chr_open() you are allowed to open non-existent devices (so
> > that you can create new devices if desired).
> >
> >When was the last time you ran vgscan and/or rebooted? Did you do anything
> >strange in the meantime?
>
> I had just rebooted before I ran pvmove. The vg0 vg is definately a
> valid vg ... I think I ran vgscan during the process of trying to get it
> all to work, and nothing strange came up ...
>
> I'll be away for the next couple of days, so I won't be recieving email
> during that time ...
>
> Thanks,
>
> Timshel
Ahh .... might help if the volume was actually active :-)
I kind of assumed that the volume would have to be inactive to move
physical extents ... you'll notice that I did a `vgchange -a n vg0' in
the script - I just moved my /var logical volume with no problems.
Maybe you want to document this a bit better ;-) I didn't notice
anything saying that the volume has to be active on the pvmove manpage
...
Thanks for your help,
Timshel
--
Timshel Knoll <timshel@pobox.com> for Debian email: <timshel@debian.org>
Geomatics/Computer Science double degree, RMIT
Debian GNU/Linux developer, see http://people.debian.org/~timshel/
For GnuPG public key: finger timshel@debian.org
prev parent reply other threads:[~2001-06-09 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-08 14:40 [linux-lvm] pvmove failure Timshel Knoll
2001-06-08 15:08 ` AJ Lewis
2001-06-09 0:11 ` Andreas Dilger
2001-06-09 0:38 ` [linux-lvm] " Timshel Knoll
2001-06-09 0:48 ` Timshel Knoll
2001-06-09 1:13 ` Timshel Knoll [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=20010609111303.A30742@knoll.ln \
--to=timshel@pobox.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 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.