ubuntu guest's file system becoming read only

[U JAGAN MOHAN]

9.3.189.114 (root/.pasroot) (Host Machine)
Run the follwoing command to go to the guest victim machine from (/var/lib/libvirt/images/jagan/new_ubuntu_alpha1)

qemu-system-ppc64 -enable-kvm -M pseries -cpu POWER8 -smp 1 -m 10G -nographic -nodefaults -monitor stdio -serial pty -append "root=/dev/sda" -kernel trusty-server-cloudimg-ppc64el-vmlinuz-generic -device spapr-vscsi -device spapr-vlan,netdev=net0,mac=6c:ae:8b:69:16:15 -netdev bridge,br=virbr0,id=net0 -drive file=trusty-server-cloudimg-ppc64el.img.qcow2

after this command you will get the screen number.
example:

QEMU 1.6.0 monitor - type 'help' for more information
(qemu) char device redirected to /dev/pts/16 (label serial0)

Then open another host session and execute the below command

# screen /dev/pts/16
(qemu)

Here the screen number is /dev/pts/16

-->>Then you will get a blank screen so press ENTER key.

The guest machine login: ubuntu/passw0rd

Then do --->sudo -i

Environment:
===========
Host: Power8
Guest : ubuntu hosted on Power8

The issue:
======
After logging into the guest some times it becomes read - only file system.

Description:
===========

Here i am not able to create directory or a file.

root@ubuntu:/opt/ltp# cat /etc/issue
Ubuntu Trusty Tahr (development branch) \n \l=====================>>ubuntu guest

root@ubuntu:~# ifconfig
eth0 Link encap:Ethernet HWaddr 6c:ae:8b:69:16:15
          inet addr:192.168.122.131 Bcast:192.168.122.255 Mask:255.255.255.0
          inet6 addr: fe80::6eae:8bff:fe69:1615/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:72 errors:0 dropped:4 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6764 (6.7 KB) TX bytes:3914 (3.9 KB)
          Interrupt:22

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:65536 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

root@ubuntu:/opt/ltp# ./runltp -f timers -p -l timers.log -o timers.out
cat: /opt/ltp/Version: No such file or directory
INFO: creating /opt/ltp/results directory
mktemp: failed to create directory via template â/tmp/ltp-XXXXXXXXXXâ: Read-only file system======>>error
FATAL: Unable to make temporary directory:

root@ubuntu:/opt/ltp# df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda 51573372 1303052 47632556 3% /
none 4 0 4 0% /sys/fs/cgroup
devtmpfs 5161908 296 5161612 1% /dev
none 1032440 184 1032256 1% /run
none 5120 0 5120 0% /run/lock
none 5162192 0 5162192 0% /run/shm
none 102400 0 102400 0% /run/user

root@ubuntu:/opt/ltp# mkdir -m 777 jagan
mkdir: cannot create directory âjaganâ: Read-only file system========>>error

root@ubuntu:/opt/ltp# touch jagan
touch: cannot touch âjaganâ: Read-only file system============>>error

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1267712

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[U JAGAN MOHAN (jamohan2)]

I am unable to run the "apport-collect 1267712" command due to the below issue.

root@ubuntu:/opt/ltp# apport-collect 1267712
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

root@ubuntu:/opt/ltp# sudo apt-get install python-apport
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.

root@ubuntu:/opt/ltp# apport-collect 1267712
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

[Shrinivas Kulkarni (shrikltc)]

Seen same Read-Only file system issue after upgrading kernel from 3.13.0-0-generic to 3.13.0-5-generic.

After kernel upgrade Guest OS system goes into Read-Only mode.

As soon as I log in from console system throws Read-Only system error :

[root@localhost ~]# virsh console shri_ubuntu_alpha1
Connected to domain shri_ubuntu_alpha1
Escape character is ^]

Ubuntu Trusty Tahr (development branch) ubuntu hvc0

ubuntu login: ubuntu
Password:
Unable to setup logging. [Errno 30] Read-only file system: '/var/log/landscape/sysinfo.log'
run-parts: /etc/update-motd.d/50-landscape-sysinfo exited with return code 1
/usr/lib/update-notifier/update-motd-fsck-at-reboot: 33: /usr/lib/update-notifier/update-motd-fsck-at-reboot: cannot create /var/lib/update-notifier/fsck-at-reboot: Read-only file system
                                                                                                                   <------------------------- Read-Only FS
ubuntu@ubuntu:~$

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.13.0-5-generic #20-Ubuntu SMP Mon Jan 20 20:03:57 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@ubuntu:~$
ubuntu@ubuntu:~$

[Anton Blanchard (anton-samba)]

Massive amounts of file corruption, it looks like you were running LTP at the time. Did you forcibly shutdown the partition?

[Abdul (abdhalee)]

Hello,

I could still reproduce this issue with alpha3 with out running any test suite as shuch, but by just updgrading the os using 'apt-get dist-upgrade' and reboot will make the guest file system read-only.

uname -r
3.13.0-12-generic

user@spartan:~$ mount
/dev/vda2 on / type ext4 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/cgroup type tmpfs (rw)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type devtmpfs (rw,mode=0755)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
none on /run/shm type tmpfs (rw,nosuid,nodev)
none on /run/user type tmpfs (rw,noexec,nosuid,nodev,size=104857600,mode=0755)
none on /sys/fs/pstore type pstore (rw)
systemd on /sys/fs/cgroup/systemd type cgroup (rw,noexec,nosuid,nodev,none,name=systemd)

mount: warning: /etc/mtab is not writable (e.g. read-only filesystem).
       It's possible that information reported by mount(8) is not
       up to date. For actual information about system mount points
       check the /proc/mounts file.

few error messages after reboot in dmesg logs:

ient.action" pid=580 comm="apparmor_parser"
[ 10.271893] init: dmesg main process (604) terminated with status 7
[ 10.462209] init: plymouth-stop pre-start process (671) terminated with status 1
[ 107.678395] random: nonblocking pool is initialized
[ 305.126848] EXT4-fs (vda2): error count: 48
[ 305.126859] EXT4-fs (vda2): initial error at 1393635308: htree_dirblock_to_tree:920: inode 4590544: block 18359106
[ 305.126865] EXT4-fs (vda2): last error at 1393825896: ext4_remount:4813: inode 4590473: block 18359087

Please have a look, and let me know if you need more details

Thanks

[Praveen (praveen-pandey)]

Hi ,

  is there any update on this bug ? becuase this is again repoducible on 3.13.0-12-generic kernel (beta1 dailybuild) .

Regards
Praveen

[Praveen (praveen-pandey)]

soory ,in previous comment there is a typo miss for kernel version it is 3.13.0-16-generic

[Diane Brent (drbrent)]

This defect was reproduced on several build levels. Moved from incomplete as no more indication of what development add'l info dev needs. I was going to make this CRITICAL also, but can't seem to change that setting. Not sure why. I can change others...

[Kalpana S Shetty (kalshett)]

Looks like Diane is unable to change this to "critical". This needs to be tracked manually.

[Breno Leitão (breno-leitao)]

Please, let's track all the read-only mount defect on the bug 1283129. Since this bug is not easily reproducible and the problem is the same, I will mark this as a dup for bug 1283129.

[Breno Leitão (breno-leitao)]

Also, this bug is not on tasty taco but on the public launchpad area.

[spike speigel (frail-knight)]

I am experiencing this issue every time I boot shortly after logging in (~7 min). I'm on a physical intel machine, not a VM, running 14.04.2 LTS, kernel 3.13.0-53-generic

BUT I've also experienced this on:

3.13.0-54-generic
3.13.0-55-generic

The two previously referenced bugs are not found...

bug 1283129
bug 1283129

I've not been able to locate any log info on this issue. How can I help. This is extremely annoying. My system is unusable in this state.