WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: Anton Khalikov <anton@xxxxxxxxxxx>
Subject: Re: [Xen-users] LVM2 snapshots and XEN = problem :(
From: Matt Ayres <matta@xxxxxxxxxxxx>
Date: Tue, 23 May 2006 08:25:09 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 23 May 2006 05:27:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4472FC67.6040404@xxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: TekTonic
References: <4472F7A2.3050701@xxxxxxxxxxx> <4472F857.6090605@xxxxxxxxxxxx> <4472FC67.6040404@xxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.2 (Windows/20060308)


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