So I'm the OP on this bug report from what seems like ages ago...
While a lot of hard work as been done by some of the members posting
here to try and replicate it, it's been very difficult to track the
specific event that has been causing this.While we "fixed" our
problem a long time ago by mo
I downloaded the 3.16-39 kernels and files and applied them to a test
system we have running on Hyper-V.I'm not able to get the -39 kernel
to fully boot. The startup hangs on the following line:
EXT4-fs (sda2) re-mounted. Opts: errors=remount-ro
If I restart the system with kernel -38, I ca
Thanks! So, 3.19 kernel runs fine. Something is wrong with the 3.16
build.I show the VSS and KVP daemons registered as well. I'm going
to let this run a few days and see what happens. I should start to see
the errors during VSS backup tonight if they occur. I may apply this
kernel to a
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.91
I wanted to give an update into testing the Vivid kernel on 14.04 LTS
re: https://bugs.launchpad.net/bugs/1454758
Our non-critical database production server ran for almost two weeks,
but this morning finally died when the file system went RO overnight due
to VSS backups. This is with the vivid-
5 matches
Mail list logo
