--J2SCkAp4GZ/dPZZf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello,

I think we just trapped into the same trouble with pvmove as described in=


https://bugzilla.redhat.com/show_bug.cgi?id=3D602516
https://bugzilla.redhat.com/show_bug.cgi?id=3D706036
etc.

Comment says, that
> I found a series of problems with pvmove which I have fixed in the upstre=
am
> repository. However, I would like to wait some time to see that no unint=
ended
> side-effects show up before seeing the change back-ported to RHEL. An au=
dit
> for similar bugs found a problem in lvremove, which I have also fixed.
> lvconvert still needs to be audited.


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.


Thanks,
Sergey

--J2SCkAp4GZ/dPZZf
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAk4UMIYACgkQfKHnntdSXjSrNQQA1VUekaYX7C1n1u/fEuWF wNIk
oUxXXvwja8ICVuS7/3Ofy1/ahtDh/YSxj7pN91geIRPgP1fMkxepl52R5Qvw xuky
+dcT+qTfihWEzaho/OH3YgpzJ6/3+LC4EszPnjqfHBCNR831LbnlvqeuOOX4 LTlW
XO7kxlGxwWmtqWslpaM=
=iwTa
-----END PGP SIGNATURE-----

--J2SCkAp4GZ/dPZZf--

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=l vm2
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.)

Alasdair

--
lvm-devel mailing list
lvm-devel [at] redhat.com
https://www.redhat.com/mailman/listinfo/lvm-devel

--tKW2IUtsqtDRztdT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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=3D602516
> > https://bugzilla.redhat.com/show_bug.cgi?id=3D706036
> >
> > 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=3 Dlvm2
> 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

--tKW2IUtsqtDRztdT
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iJwEAQECAAYFAk4USSYACgkQfKHnntdSXjTGbwP/RADyjDMsM2qcT172Dw1I XbZ5
jdfeNqIV4QIAgL4CjQhrCVU1UL9YBPsGZSvhDElr2hUXaQcIksq0bJJn1HaU eXt0
rCKp4G8I1Z+GIrqTAdtY2uOEmzwm5v/THhLfp0dsQGM9wnIHoCt5QywLUjY1 +MR7
xBDBp1aNWwl13JNrOcA=
=XMEZ
-----END PGP SIGNATURE-----

--tKW2IUtsqtDRztdT--