Filesystem becomes read-only while in use

[Ian De Silva]

I'm running Ubuntu GNOME 16.10. After updating to kernel 4.8.0-49.52 (and subsequently to 4.8.0-51.54) via apt, my file system switches to read-only during use. This bug does not occur on kernel 4.8.0-46.49 (the linux-image-4.8.0-46-generic package).

Also, note, I'm running with an encrypted filesystem (LUKS with LVM) on a dual-boot machine with a large SSD. I followed these instructions: https://askubuntu.com/questions/293028/how-can-i-install-ubuntu-encrypted-with-luks-with-dual-boot

The bug takes a while to manifest. I'm not certain how long. The only consistent behavior pattern I've observed is that the system suspended (often for a few hours/overnight), works for a while, and then, while working within Atom or IntelliJ, the filesystem, unexpectedly, becomes read-only. Sometimes the entire system hangs while other times I still have a somewhat working terminal. If I manage to trigger a reboot, the system hangs midway through it.

Ubuntu version: 16.10 (Ubuntu GNOME)

System: Dell XPS 9550
Storage info:
    *-storage
       description: Non-Volatile memory controller
       product: NVMe SSD Controller
       vendor: Samsung Electronics Co Ltd
       physical id: 0
       bus info: pci@0000:04:00.0
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: storage pm msi pciexpress msix nvm_express bus_master cap_list
       configuration: driver=nvme latency=0
       resources: irq:16 memory:de400000-de403fff ioport:c000(size=256)

I've also attached the kernel log. It seems like around 11:42 the system had a hard time finding files and at 11:41:50 we see the the file system remounted read only.

Any help you could provide would be greatly appreciated! Thanks!
-Ian

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.8.0-46-generic 4.8.0-46.49
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: desilvai 1630 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon May 8 11:42:52 2017
HibernationDevice: RESUME=UUID=c3f8c23a-ad61-4e97-9215-577f9d5cf9e7
InstallationDate: Installed on 2016-10-31 (189 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:21d4 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp.
 Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 15 9550
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic.efi.signed root=/dev/mapper/cryptovg-lv_root ro cryptopts=target=cryptoroot,source=/dev/disk/by-uuid/a20274d1-2c9f-4eca-bec5-4107099610e7,lvm=cryptovg quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-46-generic N/A
 linux-backports-modules-4.8.0-46-generic N/A
 linux-firmware 1.161.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

OK, can you test the kernel in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/comments/61?

[Ian De Silva (desilvai)]

Thanks @kaihengfeng!

I installed it and have been using the new kernel for the better part of the day (about 13 hours, 8 of which was active-use time). No issues thus far.

[Kai-Heng Feng (kaihengfeng)]

Thanks for your testing!
Can you update your status on LP: #1678184 and mark this one as duplicate?