From: noah <noah123@gmail.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, 5 Sep 2007 15:37:22 +0200 [thread overview]
Message-ID: <d00698fb0709050637p6d239d78l71b3ad932d290744@mail.gmail.com> (raw)
In-Reply-To: <46DEA19C.9000207@redhat.com>
2007/9/5, Bryn M. Reeves <breeves@redhat.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> noah wrote:
> > This patch is already applied on the kernel i was running.
> > Also, I'm not sure I'm using dm-raid at all since I don't have one of
> > these lame software (BIOS) RAID cards.
>
> dm-raid1 is nothing to do with dmraid per-se (it's just one of the
> targets dmraid might use to construct a raid set).
>
> It is also used by pvmove - when you pvmove a volume, a temporary mirror
> is constructed using dm-raid1, synchronised and then broken. After the
> pvmove the newly sync'ed copy is substituted for the original PV.
I see, thanks for the explaination.
>
> > I'm using md and dm-crypt straight on top of the harddrives.
>
> I'm not sure I understand - if you're only using md and dm-crypt, why is
> pvmove involved?
Sorry, I forgot to mention LVM. Just wanted to make it clear I wasn't
using dmraid in case it was related -- which it obviously wasn't.
>
> You can directly view the status of the mirror/pvmoved volume using
> "dmsetup status" - the patch I linked to earlier corrected a problem
> with the status report that prevented userspace correctly parsing the
> status updates.
Interesting.
Unfortunately my whole system went away in the crash and I cannot
reproduce the error again to see what dmstatus table would have
reported.
But it does look good on the new system with the same kernel AFAICT.
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
>
> It does sound from your description like you may have hit a separate
> problem since you mention that the pvmove does initially proceed correctly.
Check.
Is this list the correct place for bug reports or should I resend my
mail to dm-devel@ or even lkml?
-- noah
next prev parent reply other threads:[~2007-09-05 13:37 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 [this message]
2007-09-05 15:04 ` Bryn M. Reeves
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=d00698fb0709050637p6d239d78l71b3ad932d290744@mail.gmail.com \
--to=noah123@gmail.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).