From: Aran Cox <acox@ia.primustel.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] some issues with pvmove
Date: Mon, 13 Dec 2004 10:37:23 -0600 [thread overview]
Message-ID: <1102955844.3579.116.camel@benway> (raw)
In-Reply-To: <20041209204334.GA11338@agk.surrey.redhat.com>
On Thu, 2004-12-09 at 20:43 +0000, Alasdair G Kergon wrote:
> On Thu, Dec 09, 2004 at 02:13:03PM -0600, Aran Cox wrote:
> > I've been working on lvmove, a frontend to pvmove that I've used in the
> > past with LVM1 systems to re-organize the layout of logical volumes in a
> > volume group. I keep getting failures with pvmove that require
> > restoring metadata from backup.
>
> Try to get full diagnostics from the simplest case you can which
> causes it to fail: turn on debug-to-file in lvm.conf:
> log {
> file="/tmp/lvm2.log"
> level=7
> activation=1
> }
> then when it crashes, grab the current metadata
> with vgcfgbackup [may need -P if it's corrupt]
> (and check against /etc/lvm/backup/<vgname>)
>
> [If machine hangs you'll may have to set activation=0
> but that loses some of the debug info we want]
>
> and dump the device-mapper status:
> dmsetup info -c
> dmsetup status
> dmsetup table
>
> Alasdair
Basically I ended up buying a new HD and after adding that to the VG I
never triggered that bug again. I intend to try a similar re-
organization on a lab machine some time soonish. If I trigger any such
bugs in the future I'll try and collect all of the above info before
posting.
--
Aran Cox <acox@ia.primustel.com>
prev parent reply other threads:[~2004-12-13 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 20:13 [linux-lvm] some issues with pvmove Aran Cox
2004-12-09 20:43 ` Alasdair G Kergon
2004-12-13 16:37 ` Aran Cox [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=1102955844.3579.116.camel@benway \
--to=acox@ia.primustel.com \
--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 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.