unexpected change of file-system to read-only in KVM guest

[AlexanderYT]

dmesd from hardware node is attached

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Oct 21 18:15 seq
 crw-rw---- 1 root audio 116, 33 Oct 21 18:15 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Mon Oct 24 21:48:31 2016
HibernationDevice: RESUME=/dev/mapper/RAID6-swap
InstallationDate: Installed on 2016-08-09 (76 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HP ProLiant DL380 Gen9
PciMultimedia:

ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic.efi.signed root=/dev/mapper/RAID6-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-45-generic N/A
 linux-backports-modules-4.4.0-45-generic N/A
 linux-firmware 1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2015
dmi.bios.vendor: HP
dmi.bios.version: P89
dmi.chassis.type: 23
dmi.chassis.vendor: HP
dmi.modalias: dmi:bvnHP:bvrP89:bd05/06/2015:svnHP:pnProLiantDL380Gen9:pvr:cvnHP:ct23:cvr:
dmi.product.name: ProLiant DL380 Gen9
dmi.sys.vendor: HP

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Do you have a way to reproduce this bug, or was it a one time event?

[AlexanderYT (arcam)]

I haven't. Only one time event.

[AlexanderYT (arcam)]

same trouble in another hostsystem

[10447601.857647] device eth2 entered promiscuous mode
[10447602.670497] device eth2 left promiscuous mode
[10447605.237668] device eth2 entered promiscuous mode
[10447607.494346] device eth2 left promiscuous mode
[10447653.988207] device eth2 entered promiscuous mode
[10447654.387862] device eth2 left promiscuous mode
[10447671.111677] device eth2 entered promiscuous mode
[10447722.118606] device eth2 left promiscuous mode
[10448325.854255] device eth2 entered promiscuous mode
[10448335.981202] device eth2 left promiscuous mode
[10448339.441939] device eth2 entered promiscuous mode
[10448348.028571] device eth2 left promiscuous mode
[10448466.690902] Bluetooth: Core ver 2.21
[10448466.690933] NET: Registered protocol family 31
[10448466.690935] Bluetooth: HCI device and connection manager initialized
[10448466.690940] Bluetooth: HCI socket layer initialized
[10448466.690943] Bluetooth: L2CAP socket layer initialized
[10448466.690951] Bluetooth: SCO socket layer initialized
[10448467.102561] device eth0 entered promiscuous mode
[10448467.114680] device eth0 left promiscuous mode
[10448474.962444] device eth0 entered promiscuous mode
[10448474.986559] device eth0 left promiscuous mode
[10454099.278531] device eth2 entered promiscuous mode
[10454117.374388] device eth2 left promiscuous mode
[10454137.201176] device eth2 entered promiscuous mode
[10454155.596445] device eth2 left promiscuous mode
[10454163.812719] device eth2 entered promiscuous mode
[10454196.874666] device eth2 left promiscuous mode
[10457091.650490] EXT4-fs (dm-8): VFS: Can't find ext4 filesystem
[10457091.655775] EXT4-fs (dm-8): VFS: Can't find ext4 filesystem
[10457091.660769] EXT4-fs (dm-8): VFS: Can't find ext4 filesystem
[10457091.666027] FAT-fs (dm-8): invalid media value (0x00)
[10457091.669321] FAT-fs (dm-8): Can't find a valid FAT filesystem
[10457091.712139] XFS (dm-8): Invalid superblock magic number
[10457091.714517] FAT-fs (dm-8): invalid media value (0x00)
[10457091.717532] FAT-fs (dm-8): Can't find a valid FAT filesystem
[10457091.720907] VFS: Can't find a Minix filesystem V1 | V2 | V3 on device dm-8.
[10457091.722106] hfsplus: unable to find HFS+ superblock
[10457091.723513] qnx4: no qnx4 filesystem (no root dir).
[10457091.728240] ufs: You didn't specify the type of your ufs filesystem

                  mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

                  >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[10457091.743918] ufs: ufs_fill_super(): bad magic number
[10457091.754072] ISOFS: Unable to identify CD-ROM format.
[10457091.755475] hfs: can't find a HFS filesystem on dev dm-8
[10457091.993337] EXT4-fs (dm-7): VFS: Can't find ext4 filesystem
[10457091.998068] EXT4-fs (dm-7): VFS: Can't find ext4 filesystem
[10457092.003184] EXT4-fs (dm-7): VFS: Can't find ext4 filesystem
[10457092.007918] FAT-fs (dm-7): invalid media value (0x00)
[10457092.010928] FAT-fs (dm-7): Can't find a valid FAT filesystem
[10457092.018658] XFS (dm-7): Invalid superblock magic number
[10457092.022509] FAT-fs (dm-7): invalid...

[AlexanderYT (arcam)]

uptime
 19:18:50 up 121 days, 1:10, 2 users, load average: 0.72, 0.69, 0.90

uname -r
4.4.0-28-generic

[Joseph Salisbury (jsalisbury)]

So does it take about 121 days for the bug to happen?

[AlexanderYT (arcam)]

I'm not sure.

[AlexanderYT (arcam)]

Аgain. Another host system (Proliant DL 380-G5)

uname -r
4.4.0-46-generic

uptime
 21:05:16 up 11 days, 1:15, 1 user, load average: 0.00, 0.43, 0.89