Comment 32 for bug 1445195

1st Night Backups Ran okay, with no strange SCSI errors. The following was logged into syslog:

May 28 00:01:22 test Hyper-V VSS: VSS: op=FREEZE: succeeded
May 28 00:01:21 test kernel: [22188.912452] sd 0:0:0:0: [storvsc] Sense Key : Unit Attention [current]
May 28 00:01:21 test kernel: [22188.912465] sd 0:0:0:0: [storvsc] Add. Sense: Changed operating definition
May 28 00:01:21 test kernel: [22188.912596] 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.
May 28 00:01:21 test Hyper-V VSS: VSS: op=THAW: succeeded
May 28 00:17:01 test CRON[1323]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 28 01:17:01 test CRON[1329]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 28 01:36:17 test kernel: [27884.812212] sd 0:0:0:0: [storvsc] Sense Key : Unit Attention [current]
May 28 01:36:17 test kernel: [27884.812229] sd 0:0:0:0: [storvsc] Add. Sense: Changed operating definition
May 28 01:36:17 test kernel: [27884.812361] 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.

So we're still getting the messages about, hey, something changed on the Disk, but I can live with that for the price of a proper VSS snapshot.

Again, this is with the 3.19 -39 kernel on 14.04.2 LTS. I'll keep an eye on it. I guess I'll wait for production changes, but it's so tempting :-)