From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] pvmove hung on 2.6.22 (ubuntu gutsy)
Date: Wed, 05 Sep 2007 16:04:08 +0100 [thread overview]
Message-ID: <46DEC568.2050500@redhat.com> (raw)
In-Reply-To: <d00698fb0709050637p6d239d78l71b3ad932d290744@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
noah wrote:
> aes-root: 0 6291456 linear 9:2 384
> aes-root: 6291456 2097152 linear 9:2 887095680
> aes-root: 8388608 2097152 linear 9:2 897941888
> raidB: 0 586113528 crypt aes-cbc-essiv:sha256
> 00000000000000000000000000000000 0 9:1 1032
> raidA: 0 976771960 crypt aes-cbc-essiv:sha256
> 00000000000000000000000000000000 0 9:0 1032
Yep - that all looks normal, the devices with "linear" in the 4th field
are your regular logical volumes, then there are two crypts as well.
During a pvmove, the linear mappings will change to mirror mappings.
E.g. on a test box here, I have a VG named "t1" with an LV named "l0"
backed by two loop devices (only one is in use initially):
t1-l0: 0 4194304 linear
During a pvmove, the LV being moved would have its linear status line
replaced with a status line like this:
t1-pvmove0: 0 4194304 mirror 2 7:0 7:1 720/4096 1 AA 1 core
The 720/4096 is the progress - we've sync'ed 720 out of 4096 mirror
regions on the device. Running status repeatedly I see:
t1-pvmove0: 0 4194304 mirror 2 7:0 7:1 904/4096 1 AA 1 core
[...]
t1-pvmove0: 0 4194304 mirror 2 7:0 7:1 2557/4096 1 AA 1 core
Etc. If you are still able to reproduce the pvmove problem you can use
this to see if it's the status line bug in 2.6.22.
If not, as you describe the pvmove as hanging, a set of sysrq-t data
would be helpful to see where it's getting stuck. You can trigger this
from the keyboard or via /proc/sysrq-trigger.
The output will be sent to dmesg/syslog - it's likely to be very large,
so better to put it on something like pastebin than send it to the list.
It's most useful if you collect two sets, 5-10 seconds apart as this
allows to see if things are really stuck.
> Check.
> Is this list the correct place for bug reports or should I resend my
> mail to dm-devel@ or even lkml?
Yes - definitely the right place!
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFG3sVo6YSQoMYUY94RAskyAKCmmLYWDwSSQ+i0rG5H6W0qgoEEAwCfUnje
MDfXUHIXwT7dVmshka6AOAM=
=RAhk
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-09-05 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 17:19 [linux-lvm] pvmove hung on 2.6.22 (ubuntu gutsy) noah
2007-09-01 19:08 ` Hannes Dorbath
2007-09-01 23:05 ` noah
2007-09-05 9:57 ` noah
2007-09-05 10:06 ` Bryn M. Reeves
2007-09-05 11:42 ` noah
2007-09-05 12:31 ` Bryn M. Reeves
2007-09-05 13:37 ` noah
2007-09-05 15:04 ` Bryn M. Reeves [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=46DEC568.2050500@redhat.com \
--to=breeves@redhat.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 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).