Comment 307 for bug 1470250

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)