Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Alasdair Kergon <agk@redhat.com>,
	linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
	lvm-devel@redhat.com
Subject: Re: `pvmove stuck' in RH bugzilla
Date: Wed, 6 Jul 2011 14:38:14 +0300	[thread overview]
Message-ID: <20110706113814.GA3215@swordfish.minsk.epam.com> (raw)
In-Reply-To: <20110706112359.GF5448@agk-dp.fab.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1512 bytes --]

On (07/06/11 12:23), Alasdair G Kergon wrote:
> On Wed, Jul 06, 2011 at 12:53:10PM +0300, Sergey Senozhatsky wrote:
> > I think we just trapped into the same trouble with pvmove as described in 
> > https://bugzilla.redhat.com/show_bug.cgi?id=602516
> > https://bugzilla.redhat.com/show_bug.cgi?id=706036
> > 
> > Alasdair, could you please point are those patches in vanilla kernel 
> > (3.0-rc*) or linux-next, or some RH internal tree? 
> > This is not critical, though I'd like to try out patches.
>  
> This is a userspace bug not a kernel one.
> There is a workaround, which is to perform the pvmove one LV at a time
> using the --name option.  (For each LV, run pvmove -n <lvname>.)
> 
> The patched code is in the upstream lvm2 repository:
>   git://sources.redhat.com/git/lvm2
>   http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/doc/?cvsroot=lvm2
>   http://sourceware.org/lvm2/
> 
> It was only last night that the code incorporating these changes passed
> our public testsuite for the first time, so I think it is still
> premature to be using this on production systems.  But this means I hope
> to be in a position to make the first development release containing a
> fix for the problems quite soon.  (I added assertions to catch other
> instances of the related problems - it was more than just pvmove
> affected.)
> 

Thanks a lot for your reply.
We don't have a production machines here (just internal servers),
so I guess I could give it a try.


Best,
	Sergey

[-- Attachment #2: Type: application/pgp-signature, Size: 316 bytes --]

      reply	other threads:[~2011-07-06 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06  9:53 `pvmove stuck' in RH bugzilla Sergey Senozhatsky
2011-07-06 11:23 ` Alasdair G Kergon
2011-07-06 11:38   ` Sergey Senozhatsky [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=20110706113814.GA3215@swordfish.minsk.epam.com \
    --to=sergey.senozhatsky@gmail.com \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=lvm-devel@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