From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 18 15:45:59 2013 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CB7C9606 for ; Wed, 18 Sep 2013 15:45:59 +0000 (UTC) (envelope-from vvm@tut.by) Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5DCEE2315 for ; Wed, 18 Sep 2013 15:45:58 +0000 (UTC) Received: by mail-wg0-f42.google.com with SMTP id m15so5904897wgh.1 for ; Wed, 18 Sep 2013 08:45:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tut.by; s=google; h=message-id:from:to:references:subject:date:mime-version :content-type:content-transfer-encoding; bh=BN4O8lI7J9VOfXYpqHeUEUlsw5IWs1yUYfVTP6eZX2g=; b=lZdrC9ZxnuRpINk6Z4sQmujUTZMHQKeNuntapM47lRdDBsBdqfdNTiNX/iVMnk5era 3eRRbCbUz2ncPrJnET64CpXu9EIpiI9aHrxzjvDwttu+n/dfFLzUG0XEe6Ejt1LHkB4M HHVW5nGeS+D6f3GFQ+3qE6FH0cFETZu6EkhQY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:from:to:references:subject:date :mime-version:content-type:content-transfer-encoding; bh=BN4O8lI7J9VOfXYpqHeUEUlsw5IWs1yUYfVTP6eZX2g=; b=ISuhOlkl4eB/vtyTtfwTJMbuCJriMOgTN+8R6h5zkQF/xT7UfKqh01xfLamPW2WuA9 pAUc+ttwM6bDrPBO0RZIDFwmCS7Xns5z+u/DPGYg5yYEEzw4+qDu7bKG8hY+ERtM626j 98GT1KTTlu1awaFgTSyY5LF+Tl7pvEFQfWMm0eHF0csb2YlsQF+X/I7TR4z5JG7PO372 TSWVtqNUk1MTuouTAzSuymAiOzWNzYRFxBxPUIwzSWywfYn3kfurK2pxFJO2JiiL7oW7 m3n1DSrfsdfUnIS7rARaI8w78gLHqJV5IHlyT/7PEVlYz/zUDO2ysBSWWfENYKbeqbka uzVw== X-Gm-Message-State: ALoCoQm9T3gaAbIKCtGzwyXY5uj7KBnSXc8upm3u6JBmODUZ3KUmob4ubTszxbgKoAgu5tA7oHuJ X-Received: by 10.194.240.129 with SMTP id wa1mr32383863wjc.31.1379519157310; Wed, 18 Sep 2013 08:45:57 -0700 (PDT) Received: from TSVVM2 (ns1.st.by. [217.23.123.90]) by mx.google.com with ESMTPSA id i8sm3278589wib.1.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 18 Sep 2013 08:45:56 -0700 (PDT) Message-ID: <72995083316B4133B0C282D493DDB128@local.st.by> From: "Victor Miasnikov" To: "Abhishek Gupta \(LIS\)" , "Karl Pielorz" , 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> Subject: turn off 220V on UPS device =} file system got corrupted Re: Hyper-V 2012 Cluster / Failover - supported? - Any known issues? Date: Wed, 18 Sep 2013 18:45:54 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.3790.4548 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4913 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Sep 2013 15:46:00 -0000 Hi! K.P.> - Pulling the power on the active node hosting both VM's (i.e. Windows K.P.> guest, and FreeBSD guest) - this showed the remaining node trying to bring K.P.> up the VM's (of which Windows came up OK, and FreeBSD [file system] 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 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 correctly - 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 part 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 virtual K.P.> disk - it appears to be trashed. You can mount it (but it understandably 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 amounts 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 ----- 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 issues? > Thanks again Karl! Yes, it should work. >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. >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 issues? > > --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 bring > 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 the > 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 you > know if we can't reproduce it again!). > > At least I know it 'should' work now :) > > Thanks, > > -Karl