From owner-freebsd-xen@FreeBSD.ORG  Mon Oct 20 14:05:58 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 03EE6261;
 Mon, 20 Oct 2014 14:05:58 +0000 (UTC)
Received: from ezwind.net (bobby.ezwind.net [199.188.211.146])
 by mx1.freebsd.org (Postfix) with ESMTP id BEEC7D04;
 Mon, 20 Oct 2014 14:05:57 +0000 (UTC)
Received: from jayPC by ezwind.net (MDaemon PRO v9.6.5)
 with ESMTP id 15-md50000166894.msg; Mon, 20 Oct 2014 09:05:43 -0500
X-Spam-Processed: ezwind.net, Mon, 20 Oct 2014 09:05:43 -0500
 (not processed: spam filter heuristic analysis disabled)
X-Authenticated-Sender: jwest@ezwind.net
X-MDRemoteIP: 97.91.122.42
X-Return-Path: prvs=1370823ff3=jwest@ezwind.net
X-Envelope-From: jwest@ezwind.net
From: "Jay West" <jwest@ezwind.net>
To: "'Mark Felder'" <feld@FreeBSD.org>,
	<freebsd-xen@freebsd.org>
References: <000001cfe3ca$8d242950$a76c7bf0$@ezwind.net>
 <5436CF13.4080509@citrix.com> <000101cfe3f1$91407da0$b3c178e0$@ezwind.net>
 <65CC3330-E22F-4253-918E-72CA9B004A81@sarenet.es>
 <1413808457.2828604.181041145.4121AB54@webmail.messagingengine.com>
 <000901cfec6e$5a15f5a0$0e41e0e0$@ezwind.net>
In-Reply-To: <000901cfec6e$5a15f5a0$0e41e0e0$@ezwind.net>
Subject: RE: disk loss
Date: Mon, 20 Oct 2014 09:13:04 -0500
Message-ID: <000f01cfec6f$f7ab7e10$e7027a30$@ezwind.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLZQaRIeWHWrqmNu5N4SPLKldtZ2QLBV7crAp5Pg98Cig4q9QHtqe+oAiJfBOaZxo12UA==
Content-Language: en-us
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Oct 2014 14:05:58 -0000


I had written....
>It'd behoove freebsd to see why there is an issue (where there is none =
with Windows or Linux Guests).

One thing I should clarify... in a Xenserver environment with iSCSI =
backed SR's and (mostly) Freebsd guests... In our setup we specifically =
set up iSCSI to be the link to the Xenserver Hypervisor pool's SR's. We =
do NOT have any of the guest OS's talking iSCSI. So long story short, =
freebsd will never see iSCSI in this case - only the pool of hypervisors =
does.

Again, I'd wager this is the most common type of setup for =
Xenserver/iSCSInas/FreeBSDguests.

Long story short, if for some reason the iSCSI connection is interrupted =
(someone trips over a cable, or the san crashes and reboots, etc.)... =
the windows and linux guests recover just fine. FreeBSD on the other =
hand, will generally still have the OS disk but any additional disks are =
unreadable. Thus, I'd suspect it has something to do with how freebsd =
handles disk I/O in a Xenserver environment (and has nothing to do with =
iscsi inside FreeBSD).

J