unfortunately still the same problem using the v4.8 tools (on 4.4 and up it doesnt remount the filesystem read-only, it just hangs on any write operation)
dmesg output: [30626.788513] hv_utils: VSS: timeout waiting for daemon to reply [30627.100164] hv_utils: VSS: Transaction not active [30813.152039] INFO: task rs:main Q:Reg:1765 blocked for more than 120 seconds. [30813.152569] Not tainted 4.8.0-040800rc1-generic #201608072231 [30813.153094] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [30813.153627] rs:main Q:Reg D ffff8b44c2657fc0 0 1765 1 0x00000000 [30813.153630] ffff8b44c14d0300 ffff8b44b2b2e9c0 00000000854a7bc8 ffff8b44b14a8000 [30813.153631] ffff8b44b14a7e78 ffff8b44ae46c2c8 ffffffffffffffff ffff8b44ae46c2e0 [30813.153632] ffff8b44b14a7e10 ffffffff94215131 ffff8b44b2b2e9c0 ffffffff94217a8a [30813.153633] Call Trace: [30813.153637] [<ffffffff94215131>] ? schedule+0x31/0x80 [30813.153639] [<ffffffff94217a8a>] ? rwsem_down_read_failed+0xfa/0x150 [30813.153640] [<ffffffff93f4c8f4>] ? call_rwsem_down_read_failed+0x14/0x30 [30813.153642] [<ffffffff93cc8090>] ? percpu_down_read+0x30/0x50 [30813.153644] [<ffffffff93e124c6>] ? __sb_start_write+0x26/0x30 [30813.153645] [<ffffffff93e0f623>] ? vfs_write+0x173/0x190 [30813.153646] [<ffffffff93e10932>] ? SyS_write+0x52/0xc0 [30813.153647] [<ffffffff94219576>] ? entry_SYSCALL_64_fastpath+0x1e/0xa8 (repeats every 120 seconds) -- 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 Vivid: In Progress Status in linux source package in Wily: 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