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-devel

RE: [Xen-users] RE: [Xen-devel] Any known block device corruptionproblem

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] RE: [Xen-devel] Any known block device corruptionproblems in 3.1.0 upto release?
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sat, 2 Jun 2007 23:38:03 +1000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 02 Jun 2007 06:36:14 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01166910@trantor>
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>
References: <AEC6C66638C05B468B556EA548C1A77D01166908@trantor><C2859831.847F%Keir.Fraser@xxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01166910@trantor>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acej9pJOFjEXA1grRAG1eqoZygIVUQAIQsXwAAPyOXYAPGZ2MAAAcVYA
Thread-topic: [Xen-users] RE: [Xen-devel] Any known block device corruptionproblems in 3.1.0 upto release?
> 
> I'll follow up shortly if I can reproduce it.
> 

I can reliably reproduce the problem by hitting the browser refresh on
the java vnc client. Sometimes I have to hit it twice but most of the
time a single browser refresh is all that's required.

Hitting the disconnect button in the java console and then reconnecting
always seems to work.

My best guess at this point is some sort of race condition in the tcp
handling code in the vnc server... although I can't reproduce it outside
the web client (I'm running over a very slow link though).

James

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

<Prev in Thread] Current Thread [Next in Thread>