I upgraded a 12.04 LTS to 14.04LTS this weekend and then applied the wily kernel update as mentioned in your mail.
But I had it go read/only again this morning.


[cid:<email address hidden>]

I have attached a screen print, if you need more, please let me know.

Herman


Op 26 jan. 2016, om 19:48 heeft Joshua R. Poulson <<email address hidden><mailto:<email address hidden>>> het volgende geschreven:

@f-bosch, @lauwersm, we appreciate your patience. We've looked into
storvsc and vss and have been trying to reproduce the problem, and while
we seem to have lowered the occurrence of the problem, have not
eliminated it.

However, since the last storvsc update, we have fixed a number of issues
in the 3.19 and 4.2 kernels. If not for a rushed CVE, those kernels
would be GA at this point, but they are going into -proposed for release
this weekend.

Since you are on 14.04, I recommend testing on the lts-wily kernels,
especially after the update goes out.

# apt-get install --install-recommends linux-virtual-lts-wily linux-
tools-virtual-lts-wily linux-cloud-tools-virtual-lts-wily

(and reboot)

This will move you to the 4.2 kernel, and after the latest update goes
out, you will be running Hyper-V components from the 4.3 upstream
kernel.

On the next point release of 14.04, the plan is to switch the
recommended kernel to lts-wily anyway, so you are just getting ahead of
the rush a little.

--
You received this bug notification because you are subscribed to the bug
report.
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

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