Date: Mon, 20 Oct 2014 09:13:04 -0500 From: "Jay West" <jwest@ezwind.net> To: "'Mark Felder'" <feld@FreeBSD.org>, <freebsd-xen@freebsd.org> Subject: RE: disk loss Message-ID: <000f01cfec6f$f7ab7e10$e7027a30$@ezwind.net> In-Reply-To: <000901cfec6e$5a15f5a0$0e41e0e0$@ezwind.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000f01cfec6f$f7ab7e10$e7027a30$>