I have two IBM HX5 nodes connected to IBM DS5300. Hyper-V 2012 cluster was built on blades. In HV cluster was made six virtual machines, connected to DS5300 via HV Virtual SAN. These VMs was formed a guest SQL Cluster. Databases' files are placed on DS5300 storage and available through VM FibreChannel Adapters. IBM MPIO Module is installed on all hosts and VMs.
SQL Server instances work without problem. But! When I try to live migrate SQL VM to another HV node an SQL Instance fails. In SQL error log I see:
2013-06-19 10:39:44.07 spid1s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.07 spid1s SQLServerLogMgr::LogWriter: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.07 spid1s Write error during log flush.
2013-06-19 10:39:44.07 spid55 Error: 9001, Severity: 21, State: 4.
2013-06-19 10:39:44.07 spid55 The log for database 'Admin' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
2013-06-19 10:39:44.07 spid55 Database Admin was shutdown due to error 9001 in routine 'XdesRMFull::CommitInternal'. Restart for non-snapshot databases will be attempted after all connections to the database are aborted.
2013-06-19 10:39:44.31 spid36s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.31 spid36s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.31 spid36s fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.32 spid36s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.32 spid36s fcb::close-flush: Operating system error (null) encountered.
2013-06-19 10:39:44.33 spid36s Starting up database 'Admin'.
2013-06-19 10:39:44.58 spid36s 349 transactions rolled forward in database 'Admin' (6:0). This is an informational message only. No user action is required.
2013-06-19 10:39:44.58 spid36s SQLServerLogMgr::FixupLogTail (failure): alignBuf 0x000000001A75D000, writeSize 0x400, filePos 0x156adc00
2013-06-19 10:39:44.58 spid36s blankSize 0x3c0000, blkOffset 0x1056e, fileSeqNo 1313, totBytesWritten 0x0
2013-06-19 10:39:44.58 spid36s fcb status 0x42, handle 0x0000000000000BC0, size 262144 pages
2013-06-19 10:39:44.58 spid36s Error: 17053, Severity: 16, State: 1.
2013-06-19 10:39:44.58 spid36s SQLServerLogMgr::FixupLogTail: Operating system error 170(The requested resource is in use.) encountered.
2013-06-19 10:39:44.58 spid36s Error: 5159, Severity: 24, State: 13.
2013-06-19 10:39:44.58 spid36s Operating system error 170(The requested resource is in use.) on file "v:\MSSQL\log\Admin\Log.ldf" during FixupLogTail.
2013-06-19 10:39:44.58 spid36s Error: 3414, Severity: 21, State: 1.
2013-06-19 10:39:44.58 spid36s An error occurred during recovery, preventing the database 'Admin' (6:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected,
contact Technical Support.
In windows system log I see a lot of warnings like this:
</Event>
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{752f0849-6201-48e9-8821-7db897a10305}, DeviceName: \Device\HarddiskVolume70.
({Device Busy}
The device is currently busy.)
There aren't any error or warning in HV hosts.