Date: Wed, 18 Sep 2013 18:18:06 +0000 From: "Abhishek Gupta (LIS)" <abgupta@microsoft.com> To: Victor Miasnikov <vvm@tut.by>, Karl Pielorz <kpielorz_lst@tdx.co.uk>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org> Subject: RE: turn off 220V on UPS device =} file system got corrupted Re: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? Message-ID: <a974e3a67ad04a4584741f8a405ee9fd@BL2PR03MB210.namprd03.prod.outlook.com> In-Reply-To: <72995083316B4133B0C282D493DDB128@local.st.by> References: <18D121A056145C32F0501114@Mail-PC.tdx.co.uk> <155969fa70a34e41a84649bf3cb81c21@BL2PR03MB210.namprd03.prod.outlook.com>, <4787C47D82401721B4C53B49@Mail-PC.tdx.co.uk> <9cabc6fbba754dd3aa357943ef82db22@BL2PR03MB210.namprd03.prod.outlook.com> <72995083316B4133B0C282D493DDB128@local.st.by>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Victor,=20
Karl is asking if high availability failover scenarios will work for FreeBS=
D VMs on Hyper-V. He was specifically interested in knowing if the power pl=
ug is pulled from the Hyper-V server then would the FreeBSD VM failover and=
restart without any issues on the failover server.=20
My response was that yes the above scenario should work.
Thanks,
Abhishek
-----Original Message-----
From: Victor Miasnikov [mailto:vvm@tut.by]=20
Sent: Wednesday, September 18, 2013 8:46 AM
To: Abhishek Gupta (LIS); Karl Pielorz; freebsd-virtualization@freebsd.org
Subject: turn off 220V on UPS device =3D} file system got corrupted Re: Hyp=
er-V 2012 Cluster / Failover - supported? - Any known issues?
Hi!
K.P.> - Pulling the power on the active node hosting both VM's (i.e. Window=
s K.P.> guest, and FreeBSD guest) - this showed the remaining node trying t=
o bring K.P.> up the VM's (of which Windows came up OK, and FreeBSD [file s=
ystem] got corrupted).
A.G.> Yes, it should work.
A.G.>My understanding is that the failover should be agnostic to the guest =
OS but there could be some integration component that we might have missed.
What _exactly_ "should work" ?
1) This issue not related Hyper-V cluster itself
!) When "Pulling the power" i.e. turn off 220V in Europa ( or 110V in USA =
) on UPS device _both_ FAT on Windows and=20
FreeBSD [file system] got corrupted
( "Windows came up OK" look like because on this VM file system is NTFS )
K.P.> Hyper-V correctly see's the node fail, and restarts both VM's on the
K.P.> remaining node. Windows 7 boots fine (says it wasn't shut down correc=
tly -
K.P.> which is correct) - but FreeBSD doesn't survive.
K.P.>
K.P.> At boot time we get a blank screen with "-" on it (i.e. the first par=
t of
K.P.> the boot 'spinner') - and nothing else.
K.P.>
K.P.> Booting to a network copy of FreeBSD and looking at the underlying vi=
rtual
K.P.> disk - it appears to be trashed. You can mount it (but it understanda=
bly
K.P.> warns it's not clean) - however, any access leads to an instant panic=
('bad
K.P.> dir ino 2 at offset 0: mangled entry').
K.P.>
K.P.> Trying to run fsck against the file system throws up an impressive am=
ounts
K.P.> of 'bad magic' errors and 'rebuild cylinder group?' prompts.
To Karl: I ask You about some details . . .
Are You see related e-mail?
Best regards, Victor Miasnikov
Blog: http://vvm.blog.tut.by/
----- Original Message -----=20
From: "Abhishek Gupta (LIS)"
To: "Karl Pielorz"
Sent: Wednesday, September 18, 2013 5:50 PM
Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known issue=
s?
> Thanks again Karl! Yes, it should work.
>My understanding is that the failover should be agnostic to the guest OS b=
ut there could be some integration component=20
>that we might have missed.
>So it would be good to get to the bottom of this.
>
> Regards,
>
> Abhishek
________________________________________
> From: Karl Pielorz
> Sent: Wednesday, September 18, 2013 7:45 AM
> To: Abhishek Gupta (LIS);
> Subject: RE: Hyper-V 2012 Cluster / Failover - supported? - Any known iss=
ues?
>
> --On 18 September 2013 14:23 +0000 "Abhishek Gupta (LIS)"
> wrote:
>
>> Hi Karl,
>>
>> Thanks for reporting the issue. Please give us some time to investigate
>> and get back to you on this. In the meantime I wanted to ask if setting
>> up a Hyper-V replica for the FreeBSD VM and then a manual failover
>> reproduces the same symptoms? Please let me know.
>
> Hi,
>
> Manual fail-over appears to work OK - in order, I tested:
>
> - Live migration from one node to the other, and back again (worked)
>
> - Stopping the cluster service on one of the nodes (i.e. from Failover
> Cluster Manager) - this showed the VM moving from the node that was
> stopped, over to the other node (again worked).
>
> - Pulling the power on the active node hosting both VM's (i.e. Windows
> guest, and FreeBSD guest) - this showed the remaining node trying to brin=
g
> up the VM's (of which Windows came up OK, and FreeBSD got corrupted).
>
>
> I've had to stop now as the guy here looking after the Synology kit on th=
e
> test network is applying a firmware update (this is apparently for some
> appletalk issue or something).
>
> I'll re-run the test after this has been done - if it still fails, I'll
> come back with a 'how to reproduce' type report (and I'll obviously let y=
ou
> know if we can't reproduce it again!).
>
> At least I know it 'should' work now :)
>
> Thanks,
>
> -Karl
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a974e3a67ad04a4584741f8a405ee9fd>