We're seeing this bug consistently (although not consistent per se - the
error does not occur immediately after boot, and doesn't immediately
disconnect the server from the network; anything from 3 weeks to 3 hours
before it starts, and a day or so after is starts before it gets
permanently disconn
After sourcing a new backup store and backing up the live data, we've
updated the server and rebooted. On mount errors were reported with the
filesystem so e2fsck used. Some errors were found and fixed, remounted,
no errors. First attempted write to the volume (a simple save of new
text file) retur
Additional: a 3rd SAN/VM pairing, part of the same wave of installation and in
most respects an identical set up is not experiencing this issue - however this
one was completed earlier in cycle so has a different kernel:
# uname -a
Linux oandata1 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:3
We're seeing errors very similar to this on 2 16.04 VMs, both attached
to different SANs. Sadly one is the live data and the other the backup,
so...
kern.log snippet:
Apr 25 14:54:52 oaebackup1 kernel: [11778105.146482] EXT4-fs (sda1): previous
I/O error to superblock detected
Apr 25 14:54:52 oa
4 matches
Mail list logo
