How about rusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
To manage notifications about this bug go
I can confirm that the trusty patches are preventing the filesystem
failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS
3.13.0-103-generic #150~lp1470250 SMP looks promising.
Several days without crash. I encountered some IO errors but the filesystem
remains rw.
[Wed Jan 11 13:47:35 2017] hv_storvsc vmbus_0_1: cmd 0x35 scsi status 0x2 srb
status 0x82
[Wed Jan 11 13:47:35 2017] hv_storvsc vmbus_0_1: stor pkt ff
The link to trusty kernels is gone :(
http://kernel.ubuntu.com/~jsalisbury/lp1470250/AlexFaulpeltzPatch/trusty/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2
Thank you for the update. I'm staying tuned :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
To manage no
No luck with 14.04. After couple of days two test machines restarted
unexpectedly at the very same moment. I sustepct kernel crash but the virtual
console is gone and nothing was logged.
On the other hand the xenial machine is working for weeks now without any
issues.
--
You received this bug
Over 24h of trusty tests under heavy load and so good so far.
IMHO the kernel patch should suffice. I don't see "trying to recover VSS
connection" messages neither on 16.04 kernel nor 14.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
The xenial kernel works like a charm since the patch. Great work! :)
I'm using application consistent backup (the Hyper-V signals snapshot to the
guest OS) rather than crash consistent (snapshoting without informing the
guest). The Hyper-h integration services in the guest are required for that
I'm really looking forward to test the path on trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
To m
Yes.
Linux backup-01 4.4.0-36-generic #55~lp1470250PatchedAlexFaulpeltz SMP Wed Aug
31 16:14:16 UTC 20 x86_64 x86_64 x86_64 GNU/Linux
Another 24h and no crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
It looks like it does the trick! Already over 90h of testing with tiobench and
it works like a charm!
Usually it took less than 4h (several at best) to crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
For the record:
The proper fix for me was to make sure that /etc/apparmor.d/usr.sbin.dhcpd
included
capability chown,
along:
capability net_bind_service,
capability net_raw,
capability setgid,
capability setuid,
For some reason it was not there after upgrade.
--
You received this bug
I got the same on 16.04 after upgrading from 15.10.
It really sucks nobody can fix it for so many years.
Use Slackware guys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186662
Title:
isc-dhcp-ser
http://orig00.deviantart.net/d4e7/f/2012/247/6/b/and_it_s_gone_by_celeith-d5div3y.jpg
(sry, couldnt' resist it :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.
Keep in mind tough that I suggested that it might be some kind of memory
corruption bug and the filesystem corruption might be just
manifestation. I experiences different problems on 3.13.0-32-generic
(random crashes and so on) thet were related to snapshoting. I guess the
vmm integration is made t
Good news.
# uname -a
Linux backup-02 3.13.0-86-generic #131~lp1470250Commitd215f91Reverted SMP Wed
May 25 20:47:20 UTC x86_64 x86_64 x86_64 GNU/Linux
It is running since Jun 7 16:30:10 and still no crash.
The only issue is that integration with VMM went awry and the hostname is
reported as:
Testing...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
Backups
To manage notifications about this bug go to:
ht
I'm having difficulties installing those packages on trusty.
I run into:
linux-tools-3.13.0-86 : Depends: binutils (>= 2.24) but it is not going to be
installed.
Depends: binutils (< 2.25) but it is not going to be
installed.
Depends: libdw1 (>=
Are you aware of the fact that I have reported errors with
3.13.0-32-generic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VS
I experienced it during migration and other means involving snapshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
What's your VSS snapshot frequency? Increasing it you can shorten the tests as
the problem should appear earlier.
I'm doing the snapshot every 15 minutes. Just snapshots, no need to do a full
backup. In my case a snapshot made for any reason (branching, moving to
different host etc.) was causin
Bad news.
I tried to replicate the test results on my own.
I downloaded and installed the first kernel marked as good:
# uname -a
Linux backup-01 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
I performed the tiobench and simultaneity the backup.
At
Which ubuntu version are you using for tests? 14.04? How about vss daemon, kvp
daemon? Have you installed them? Which version and package have you used? Are
you using crash consistent or application consistent backups (with VSS support
in the Guest Linux)?
I'd like to independently repeat your
Now I got much more verbose error:
[Wed Mar 30 11:38:59 2016] NMI watchdog: BUG: soft lockup - CPU#1 stuck for
25s! [init:1321]
[Wed Mar 30 11:38:59 2016] Modules linked in: btrfs(E) xor(E) raid6_pq(E)
ufs(E) qnx4(E) hfsplus(E) hfs(E) minix(E) ntfs(E) msdos(E) jfs(E) xfs(E)
libcrc32c(E) xt_nat
It's a regression. Anyone knows the last working kernel version?
It might be easier to find the breaking change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470250
Title:
[Hyper-V] Ubuntu 14.04.2
It looks like there is a race condition and the corruption occurs when
the FREEZE happens to late. No wonder as it's happening from userland.
Mar 16 15:06:49 emsi-02 kernel: [422953.038989] sd 2:0:0:0: [storvsc] Sense Key
: Unit Attention [current]
Mar 16 15:06:49 emsi-02 kernel: [422953.0
Lo luck here :( Even though I have the hv_vss_daemon that logs
FREEZE/THAW I experienced crashes:
Mar 15 10:36:38 emsi-02 Hyper-V VSS: VSS: op=FREEZE: succeeded
Mar 15 10:36:38 emsi-02 kernel: [320343.560935] sd 2:0:0:0: [storvsc] Sense Key
: Unit Attention [current]
Mar 15 10:36:38 emsi-02
I also found someone reporting the issue on RedHat:
https://social.technet.microsoft.com/Forums/office/en-US/cfe15e32-bfbc-47e0-8d2b-382a1293b9aa/vss-issues-with-centos-66-x64?forum=linuxintegrationservices
>From my tests it looked like Centos kernels are not affected but above
report casts some s
@f-bosch: The message is an early warning. Even on the latest 4.2.0-30
it just forecasts the imminent failure:
[Sat Feb 27 00:01:08 2016] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention
[current]
[Sat Feb 27 00:01:08 2016] sd 2:0:0:0: [storvsc] Add. Sense: Changed operating
definition
[Sat Feb
I'm on the following since Feb 20:
Linux XXX-Linux 4.2.0-30-generic #35-Ubuntu SMP Fri Feb 19 13:52:26
It still reports Add. Sense:
[Wed Feb 24 00:01:01 2016] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention
[current]
[Wed Feb 24 00:01:01 2016] sd 2:0:0:0: [storvsc] Add. Sense: Changed operating
@F-Bosch: Regarding the link going down I experienced that too. I
correlated it with IPv6. When I disabled IPv6 on the interface the
problem went away. Previously the more data I sent over ipv6 the sooner
it broke. No logs whatsoever. Migrating the machine to another host
restored the connectivity
Actually I got this on 3 VMs on my Azure Pack. One 15.10 and two 14.04.03.
On 15.10 I tried to fsck the root fs before reboot. What could go wrong as fs
is already read-only I thought.
Here is the session:
~# touch /oioi
touch: cannot touch '/oioi': Read-only file system
~# fsck /<--- At t
No luck with 4.2.0-27
# uname -a
Linux xxx 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
Just got this few days ago:
[Tue Feb 9 00:00:56 2016] sd 2:0:0:0: [storvsc] Sense Key : Unit Attention
[current]
[Tue Feb 9 00:00:56 2016] sd 2:0:0:0: [stor
33 matches
Mail list logo
