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

[Xen-users] shared storage manual remount ...

To: "Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list" <rhelv5-list@xxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] shared storage manual remount ...
From: Zoran Popović <shoom013@xxxxxxxxx>
Date: Thu, 4 Feb 2010 01:40:26 +0100
Cc:
Delivery-date: Wed, 03 Feb 2010 16:41:33 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=5gjngs6iYs86rpoRhPCul/KEAIZxa8LKXpPQfWCTmVA=; b=aSUT7WBF4gdzIUQihzNuvlhPbUZ2KcTx1SFEYzPdj2EdvXzE619kkmydMfvdbqsYHd cqp8HEkD9ZCxzGF8ui8dA/LnqvC9p6Z5T2GoXE4+Vhxe866Vt9EXf776Bl8iRuy/+R0V G3i4tDGrdhvI7tnwD5fNJ66PPfScgIR7hOTQM=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=e/C3xeSDd5MrHnsYgSg2xT+zaG7p+KVM/Jq6omTQ8w/ogmeQw/1aySZkEtjmJYGrl2 dBLPGiEHgwIFVv07wfBYdy5d8qZRlmuzvdyk/c0F0vODD53CB/ZCuMwUI+1kDXcCN/x/ +yLj91vEnLu19ciEO+25bqP+MOllymHSVy1VY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I am wondering if there is a way to solve the following problem: I suppose that the usual way is to establish distributed file system with locking mechanisms like it is possible with GFS and Red Hat Cluster Suite or similar, but I am interested in doing some of this manually and ONLY with raw devices (no file system), or simply in knowing some general principles. The case: I have a VLUN (on FC SAN) presented on two servers, but mounted only on one host - to be more precise, used by a Xen HVM guest system as a raw physical phy:// drive. Then, I put this guest down, and bring it manually up on second host - it can see changed images, and make changes to the presented disks. Then I put it down there, and bring it up again on the first host - BUT THEN, this guest (or host) doesn't see changes made by the second system, it still sees the picture as it was the way it left it.
Or even better, if I bring HVM guest on a host, then put it down, make restore of his disks on the storage (I am using HP EVA8400, restoring original disk from a snapshot - it does have redundant controllers but their cache must be in sync for sure), and then bring it up - it still sees things on the disks as they were before restore. But if I _RESTART_ the host, it can see restored disks correctly. Now, I am wondering why is this happening, and if it is possible somehow to resync with the storage without restart (I wouldn't like that on production ! and on our windows systems this is possible) ... I've tried sync (but that is like flushing buffer cache), and I didn't try echo 3 > /proc/sys/vm/drop_caches after that (I've just come upon some articles about that), and I am not sure if that would really invalidate cache and help me. What is the right way of dong this ? Please, help ...
ZP.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users