I was able to backport the two patches to Trusty. It required quite a few prerequisite commits. The following commits were backported to a Trusty test kernel:
f9cc88d lp1470250: patch from faulpeltz 6f3e8a2 Drivers: hv: utils: Continue to poll VSS channel after handling requests. 725a85d Drivers: hv: utils: fix a race on userspace daemons registration a0c12c6 Drivers: hv: kvp: fix IP Failover 51fea7d Drivers: hv: utils: Invoke the poll function after handshake 42fb309 Drivers: hv: utils: run polling callback always in interrupt context 505de58 Drivers: hv: fcopy: full handshake support 2ec9789 Drivers: hv: vss: full handshake support e12c519 Tools: hv: vss: use misc char device to communicate with kernel 1f3abc0 Drivers: hv: kvp: convert to hv_utils_transport d789589 Drivers: hv: fcopy: convert to hv_utils_transport 51ed5da Drivers: hv: vss: convert to hv_utils_transport edbff5d Drivers: hv: util: introduce hv_utils_transport abstraction 056fbb5 Drivers: hv: fcopy: switch to using the hvutil_device_state state machine 5eb0af4 Drivers: hv: vss: switch to using the hvutil_device_state state machine a170e78 Drivers: hv: kvp: switch to using the hvutil_device_state state machine a539598 Drivers: hv: fcopy: rename fcopy_work -> fcopy_timeout_work 7894b35 Drivers: hv: kvp: rename kvp_work -> kvp_timeout_work d3fc031 Drivers: hv: kvp,vss: Fast propagation of userspace communication failure ee85362 Drivers: hv: vss: Introduce timeout for communication with userspace d714c5a Tools: hv: vssdaemon: ignore the EBUSY on multiple freezing the same partition b957545 connector: add portid to unicast in addition to broadcasting The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1470250/AlexFaulpeltzPatch/trusty/ Can this kernel be tested to see if it resolves this bug? Note, that both the linux-image and linux-image-extra .deb packages need to be installed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1470250 Title: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: In Progress Bug description: Customers have reported running various versions of Ubuntu 14.04.2 LTS on Generation 2 Hyper-V Hosts. On a random Basis, the file system will be mounted Read-Only due to a "disk error" (which really isn't the case here). As a result, they must reboot the Ubuntu guest to get the file system to mount RW again. The Error seen are the following: Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense Key : Unit Attention [current] Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. Sense: Changed operating definition Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc vmbus_0_4: stor pkt ffff88006eb6c700 autosense data valid - len 18 Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense Key : Unit Attention [current] Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. Sense: Changed operating definition Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. This relates to the VSS "Windows Server Backup" process that kicks off at midnight on the host and finishes an hour and half later. Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct kernel version we have. We're currently running kernel version 3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- We see the same errors on both. As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 hyper-v system because of this. We can stop the backup process and all is good, but we need nightly backups to image all of our VM's. All the windows guests have no issues of course. We also have some CentOS based guests running without issues from what we've seen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1470250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp