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
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1267712
Title:
ubuntu guest's file system becoming read only
Status in “linux” package in Ubuntu:
Incomplete
Bug description:
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1267712/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
