Ubuntu
linux package

  1. Xenial (16.04)
  2. Bug #1470250
  3. Comment #310

Comment 310 for bug 1470250

Revision history for this message
faulpeltz (mg-h) wrote :

v4.8-rc2 (with patch 1/2 from #308) failed after 18h :(

With the first patch applied, the VSS daemon decides to quit, but a THAW is missing after the FREEZE there are the usual syscall timeouts afterwards

kernel: sd 2:0:0:0: [storvsc] Add. Sense: Changed operating definition
kernel: sd 2:0:0:0: Warning! Received an indication that the operating parameters on this target have changed. The Linux SCSI layer does not automa
kernel: hv_utils: VSS: timeout waiting for daemon to reply
kernel: hv_utils: VSS: Transaction not active
systemd[1]: hv-vss-daemon.service: Main process exited, code=exited, status=1/FAILURE
unknown[2966]: Hyper-V VSS: VSS: op=FREEZE: succeeded
systemd[1]: hv-vss-daemon.service: Unit entered failed state.
unknown[2966]: Hyper-V VSS: write failed; error: 22 Invalid argument
systemd[1]: hv-vss-daemon.service: Failed with result 'exit-code'.
kernel: hv_utils: VSS: failed to communicate to the daemon: -22