RHEL 6 Guest VM in MS Hyper-V hangs up during snapshot/backup operation

Issue

During snapshot/backup operation, RHEL 6 Guest VM in MS Hyper-V hangs up, errors similar to below are observed in logs:

Nov 23 02:32:43 server Hyper-V VSS: VSS: op=FREEZE: succeeded
Nov 23 02:32:43 server Hyper-V VSS: VSS: op=THAW: succeeded
Nov 23 02:32:44 server kernel: scsi 2:0:1:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 4
Nov 23 02:32:44 server kernel: sd 2:0:1:0: Attached scsi generic sg4 type 0
Nov 23 02:32:44 server kernel: sd 2:0:1:0: [sdd] 104857600 512-byte logical blocks: (53.6 GB/50.0 GiB)
Nov 23 02:32:44 server kernel: sd 2:0:1:0: [sdd] 4096-byte physical blocks
Nov 23 02:32:44 server kernel: sd 2:0:1:0: [sdd] Write Protect is off
Nov 23 02:32:44 server kernel: sd 2:0:1:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 23 02:32:44 server kernel: sdd: unknown partition table
Nov 23 02:32:44 server kernel: scsi 2:0:1:2: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 4
Nov 23 02:32:44 server kernel: sd 2:0:1:2: Attached scsi generic sg5 type 0
Nov 23 02:32:44 server kernel: sd 2:0:1:2: [sde] 83886080 512-byte logical blocks: (42.9 GB/40.0 GiB)
Nov 23 02:32:44 server kernel: sd 2:0:1:2: [sde] 4096-byte physical blocks
Nov 23 02:32:44 server kernel: sd 2:0:1:0: [sdd] Attached SCSI disk
Nov 23 02:32:44 server kernel: sd 2:0:1:2: [sde] Write Protect is off
Nov 23 02:32:44 server kernel: sd 2:0:1:2: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov 23 02:32:44 server kernel: scsi 2:0:1:1: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 4
Nov 23 02:32:44 server kernel: sd 2:0:1:1: Attached scsi generic sg6 type 0
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB)
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] 4096-byte physical blocks
Nov 23 02:32:44 server kernel: sde:
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Write Protect is off
Nov 23 02:32:44 server kernel: sde1
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Asking for cache data failed
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Assuming drive cache: write through
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Sector size 0 reported, assuming 512.
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] 1 512-byte logical blocks: (512 B/512 B)
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] 0-byte physical blocks
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Asking for cache data failed
Nov 23 02:32:44 server kernel: sd 2:0:1:1: [sdf] Assuming drive cache: write through
Nov 23 02:32:44 server kernel: sdf: detected capacity change from 10737418240 to 512
Nov 23 02:32:44 server kernel: sdf:
Nov 23 02:32:44 server kernel: sd 2:0:1:2: [sde] Attached SCSI disk
Nov 23 02:34:16 server Hyper-V VSS: VSS: op=CHECK HOT BACKUP
Nov 23 02:34:33 server Hyper-V VSS: VSS: op=CHECK HOT BACKUP
Nov 23 02:35:44 server udevd[694]: worker [2732] unexpectedly returned with status 0x0100
Nov 23 02:35:44 server udevd[694]: worker [2732] failed while handling '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBus:00/ed6a2243-17d2-4536-9e6d-5155c4db33cd/host2/target2:0:1/2:0:1:2/block/sde'
Nov 23 02:36:34 server kernel: INFO: task events/3:38 blocked for more than 120 seconds.
Nov 23 02:36:34 server kernel:      Not tainted 2.6.32-696.16.1.el6.x86_64 #1
Nov 23 02:36:34 server kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 23 02:36:34 server kernel: events/3      D 0000000000000003     0    38      2 0x00000000
Nov 23 02:36:34 server kernel: ffff8809f701fc80 0000000000000046 0000000000000000 ffff8809efd90b50
Nov 23 02:36:34 server kernel: ffff8806d5546b50 ffffffff81fef824 00003ec3c826ae64 ffff8809f701fc50
Nov 23 02:36:34 server kernel: ffff8809f701fc20 00000001041870c8 ffff8809f700a5f8 ffff8809f701ffd8
Nov 23 02:36:34 server kernel: Call Trace:
Nov 23 02:36:34 server kernel: [<ffffffff810af165>] async_synchronize_cookie_domain+0xb5/0x150
Nov 23 02:36:34 server kernel: [<ffffffff810a6930>] ? autoremove_wake_function+0x0/0x40
Nov 23 02:36:34 server kernel: [<ffffffff810af238>] async_synchronize_full_domain+0x18/0x20
Nov 23 02:36:34 server kernel: [<ffffffffa008cc78>] sd_remove+0x28/0xc0 [sd_mod]
Nov 23 02:36:34 server kernel: [<ffffffff8138398f>] __device_release_driver+0x6f/0xe0
Nov 23 02:36:34 server kernel: [<ffffffff81383afd>] device_release_driver+0x2d/0x40
Nov 23 02:36:34 server kernel: [<ffffffff81382a03>] bus_remove_device+0xa3/0x110
Nov 23 02:36:34 server kernel: [<ffffffff8138041d>] device_del+0x12d/0x200
Nov 23 02:36:34 server kernel: [<ffffffff813a9113>] __scsi_remove_device+0xc3/0xd0
Nov 23 02:36:34 server kernel: [<ffffffff813a9150>] scsi_remove_device+0x30/0x50
Nov 23 02:36:34 server kernel: [<ffffffffa0076487>] storvsc_remove_lun+0x67/0xa0 [hv_storvsc]
Nov 23 02:36:34 server kernel: [<ffffffffa0076420>] ? storvsc_remove_lun+0x0/0xa0 [hv_storvsc]
Nov 23 02:36:34 server kernel: [<ffffffff8109fc30>] worker_thread+0x170/0x2a0
Nov 23 02:36:34 server kernel: [<ffffffff810a6930>] ? autoremove_wake_function+0x0/0x40
Nov 23 02:36:34 server kernel: [<ffffffff8109fac0>] ? worker_thread+0x0/0x2a0
Nov 23 02:36:34 server kernel: [<ffffffff810a649e>] kthread+0x9e/0xc0
Nov 23 02:36:34 server kernel: [<ffffffff8100c28a>] child_rip+0xa/0x20
Nov 23 02:36:34 server kernel: [<ffffffff810a6400>] ? kthread+0x0/0xc0
Nov 23 02:36:34 server kernel: [<ffffffff8100c280>] ? child_rip+0x0/0x20