Re: [Xen-users] LVM2 snapshots and XEN = problem :(

[Jeff Utter <jeffutter.lists@xxxxxxxxx>]

I ran into this same problem. So... this is confirmed with the 3.0.2 
distribution off xensource.com? If i use the latest from the Mercurial 
repo, that'll fix it up?
Also, i had to power off my system to get it un-hung from this. Now it 
never picks up the lvm disk with vgscan.. it doesn't even show up in 
pvdisplay. The only way i can get it to work is to do pvs /dev/hdc; 
lvchange -a y. Did anyone else have this problem as a result of this bug 
and know how to fix it?
Thanks,
Jeff

Matt Ayres wrote:
> Anton Khalikov wrote:
> > Hello Matt
> >
> > Matt Ayres wrote:
> > > What is your dom0/domU kernel version?
> > dom0:
> > uname -a
> > Linux andrew 2.6.16-xen0 #2 Sat May 6 15:23:55 YEKST 2006 i686 GNU/Linux
> >
> > domU:
> > uname -a
> > Linux xen1 2.6.16-xenU #2 SMP Sat May 6 15:28:43 YEKST 2006 i686 
> > GNU/Linux
> > xen version 3.0.2
> It is a 2.6.16 issue.  It was fixed in 2.6.16.12. Latest Xen is 
> 2.6.16.13 from 3.0-testing.
> http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.16.12
>
>
>
> commit f6a731290ca18b31fd447989319eb913d9c308d8
> Author: Alasdair G Kergon <agk@xxxxxxxxxx>
> Date:   Mon Apr 24 13:36:06 2006 -0700
>
>     [PATCH] dm snapshot: fix kcopyd destructor
>
>     Before removing a snapshot, wait for the completion of any kcopyd 
> jobs using it. Do this by maintaining a count (nr_jobs) of how many 
> outstanding jobs each kcopyd_client has.
>     The snapshot destructor first unregisters the snapshot so that no 
> new kcopyd jobs (created by writes to the origin) will reference that 
> particular snapshot.  kcopyd_client_destroy() is now run next to wait 
> for the completion of any outstanding jobs before the snapshot 
> exception structures (that those jobs reference) are freed.
>     Signed-off-by: Alasdair G Kergon <agk@xxxxxxxxxx>
>     Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
>     Signed-off-by: Linus Torvalds <torvalds@xxxxxxxx>
>     Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users