You are not logged in.

#26 2012-12-03 21:17:31

uzsolt
Member
Registered: 2012-06-13
Posts: 56

Re: Read only filesystem problem

Do you think it's a hardware error? My hdd goes wrong? But why only on sda3? All another partitions are ok.
I did find similar reports on web and it seems it can be a bug.

Offline

#27 2012-12-04 04:21:08

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,265

Re: Read only filesystem problem

uzsolt wrote:

Do you think it's a hardware error?

No.

What is the output of mount ??
What is the output of dmesg | grep sda3  ??


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#28 2012-12-04 06:28:07

uzsolt
Member
Registered: 2012-06-13
Posts: 56

Re: Read only filesystem problem

Now?

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=2023608k,nr_inodes=505902,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda6 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct,cpu)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=26,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,size=5242880k)
/dev/sda5 on /var type ext4 (rw,relatime,data=ordered)
/dev/sda3 on /home type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /home/irando type jfs (rw,relatime)
/dev/sda2 on /backup type jfs (rw,relatime)
/dev/sda8 on /home/downloads type ext4 (rw,relatime,data=ordered)
bindfs on /home/users/zsolt/public_html/orarend/include/codeigniter type fuse.bindfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions,allow_other)
bindfs on /home/users/zsolt/public_html/orarend/include/smarty type fuse.bindfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000,default_permissions,allow_other)
[    2.497933]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[   23.962092] systemd[1]: Expecting device dev-sda3.device...
[   27.342808] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)

When this error occurs the mount options on sda3 will 'ro'.

When I run into this problem I'll post the outputs again smile

Or do you have an idea?

Offline

#29 2012-12-04 06:34:06

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 12,265

Re: Read only filesystem problem

You did not mention that this is a transient problem.  I assumed it was a persistent problem.

Yes, please post the output after the failure.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Like you, I have no idea what you are doing, but I am pretty sure it is wrong...Jasonwryan
----
How to Ask Questions the Smart Way

Offline

#30 2012-12-04 06:40:48

uzsolt
Member
Registered: 2012-06-13
Posts: 56

Re: Read only filesystem problem

I wrote "sometimes". Sorry when I was equivocal.
I'll post outputs at failure.

Offline

#31 2012-12-07 03:49:40

nstickney
Member
From: Bavaria
Registered: 2011-03-11
Posts: 5
Website

Re: Read only filesystem problem

I am having this problem as well; my SSD, however, is almost brand new. The triggering factor was that I switched to systemd. Using initscripts, everything works as advertised; using systemd, the system falls apart with the "Read-only file system" error.


http://www.stick-online.net
nstickney@elisha: Arch Linux on MacBook5,1

Offline

#32 2013-01-11 19:36:38

uzsolt
Member
Registered: 2012-06-13
Posts: 56

Re: Read only filesystem problem

uzsolt wrote:

I wrote "sometimes". Sorry when I was equivocal.
I'll post outputs at failure.

So, here it is:

[    2.488259]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 >
[   23.856358] systemd[1]: Expecting device dev-sda3.device...
[   27.502954] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[  771.888027] Aborting journal on device sda3-8.
[  771.888154] EXT4-fs (sda3): delayed block allocation failed for inode 2753083 at logical offset 5 with max blocks 2 with error -30
[  771.888159] EXT4-fs (sda3): This should not happen!! Data will be lost
[  771.888225] EXT4-fs error (device sda3) in ext4_reserve_inode_write:4550: Journal has aborted
[  771.888252] EXT4-fs (sda3): delayed block allocation failed for inode 2764900 at logical offset 4 with max blocks 7 with error -30
[  771.888256] EXT4-fs (sda3): This should not happen!! Data will be lost
[  771.888289] EXT4-fs error (device sda3) in ext4_da_writepages:2398: Journal has aborted
[  771.888304] EXT4-fs error (device sda3) in ext4_da_writepages:2398: Journal has aborted
[  771.933948] EXT4-fs error (device sda3) in ext4_da_write_end:2636: IO failure
[  771.960649] EXT4-fs error (device sda3): ext4_journal_start_sb:349: Detected aborted journal
[  771.960662] EXT4-fs (sda3): Remounting filesystem read-only
[  771.985514] EXT4-fs (sda3): ext4_da_writepages: jbd2_start: 13312 pages, ino 2753083; err -30
[  771.985525] EXT4-fs (sda3): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 2764900; err -30
[  771.985668] EXT4-fs (sda3): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 2753083; err -30

The full dmesg is here.

Offline

#33 2013-01-26 08:18:17

matej
Member
Registered: 2013-01-26
Posts: 1

Re: Read only filesystem problem

Hi,

I am having exactly the SAME issue. Have 8 guests and they are all running without any problems (nothing strange in logs...) but there is one that has those IO failures. Even though there are not messages like that in the host server, I have replaced both disks in RAID with new ones and it still happens. So I am pretty sure it's not a hardware issue.
Any ideas and suggestions to get this solved are very welcome, since there is no really useful information about it anywhere and it seems many people have this issue.

Thanks,
Matej

Offline

#34 2013-04-03 22:40:16

barrpet
Member
Registered: 2013-04-03
Posts: 1

Re: Read only filesystem problem

Possible Solution if you have a Crucial M4 SSD:
After struggling with the above errors, I may have a specific solution for some of you. I was getting I/O error dev sda bad sector warnings and a complete inability to do anything, usually after about 30 minutes to an hour after power cycling. The problem happened out of the blue one day. My Crucial M4 SSD was being remounted as read-only. Turns out there is a bug in the old firmware that causes this problem (and likewise BSOD on Windows, which I was also receiving). It only starts to happen after 5184 hours of uptime on the drive, which makes it appear to be a random issue. According to my SMART outputs, I have 7 months and 10 days of uptime on my drive (almost exactly 5184 hours). A firmware update from the Crucial website solved it for me.

Last edited by barrpet (2013-04-03 22:44:00)

Offline

Board footer

Powered by FluxBB