linux-kernel - Re: `pvmove stuck' in RH bugzilla

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110706113814.GA3215@swordfish.minsk.epam.com>
Date:	Wed, 6 Jul 2011 14:38:14 +0300
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	Alasdair Kergon <agk@...hat.com>, linux-raid@...r.kernel.org,
	linux-kernel@...r.kernel.org, lvm-devel@...hat.com
Subject: Re: `pvmove stuck' in RH bugzilla

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

Content of type "application/pgp-signature" skipped