Read-only file system

varunb · 01-21-2013, 05:50 AM

Hello,

I am using SUSE Linux Enterprise Server 10

I am not able to create files or delete files.
every time i get the error as Read-only file system.

Code:

observer:~ # touch a
touch: cannot touch `a': Read-only file system

Code:

observer:~ # df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/md0               20G   13G  6.5G  66% /
udev                  990M  156K  989M   1% /dev
/dev/md2               20G  7.8G   11G  42% /home
/dev/md3               20G  5.0G   14G  27% /srv
/dev/md6              510M   44M  441M   9% /tmp
/dev/md1              9.9G  1.1G  8.3G  12% /var
/dev/md4               20G  6.4G   13G  34% /var/lib/mysq

Code:

observer:~ # mount
/dev/md0 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/md2 on /home type ext3 (rw,acl,user_xattr)
/dev/md3 on /srv type ext3 (rw,acl,user_xattr)
/dev/md6 on /tmp type ext3 (rw,acl,user_xattr)
/dev/md1 on /var type ext3 (rw,acl,user_xattr)
/dev/md4 on /var/lib/mysql type ext3 (rw,acl,user_xattr)
securityfs on /sys/kernel/security type securityfs (rw

i did restart, also did fsck manually but still the same issue.
Any suggestions??? please.

jschiwal · 01-21-2013, 05:56 AM

Which directory are you in? It's possible that one of the drives has a problem. There is an option mount option errors={continue|remount-ro|panic}. The superblock contains the default if it isn't in /etc/fstab.

Check your kernel messages. If there is a problem mounting, there should be a message about it.

goumba · 01-21-2013, 02:37 PM

It looks like he's in /home/observer from the prompt, home being mounted rw. I will second checking dmesg for ny errors while mounting the filesystem, that's the message I got when I had problems with an fs mounting. Usualy however the fs mounted ro and I hadn't noticed.

Also, check permissions on the directory, make sure they're set properly for the user and/or group.

goumba · 01-21-2013, 02:40 PM

Two reasons I have gotten this error in the past:

1. The user did not have the proper permissions to write to the filesystem in question. Check your permissions n the directory(ies) involved. I'd check into this.

2. The fs has an error, however usually then it would be mounted ro, but following the suggestion above to check dmesg can't hurt.

varunb · 01-21-2013, 10:44 PM

Quote:

Originally Posted by jschiwal

Which directory are you in? It's possible that one of the drives has a problem. There is an option mount option errors={continue|remount-ro|panic}. The superblock contains the default if it isn't in /etc/fstab.

Check your kernel messages. If there is a problem mounting, there should be a message about it.

Only for / i.e for /dev/md0

Other directoris are fine.

refering to the below url

http://askubuntu.com/questions/19745...ly-file-system

After running the below two commands, now i am able to create a file or remove.

fsck -Af

shutdown -rF now

I have to keep it under observation. .
Thanks for the reply. .

curious95 · 01-22-2013, 12:08 AM

Quote:

Originally Posted by goumba

Two reasons I have gotten this error in the past:

1. The user did not have the proper permissions to write to the filesystem in question. Check your permissions n the directory(ies) involved. I'd check into this.

2. The fs has an error, however usually then it would be mounted ro, but following the suggestion above to check dmesg can't hurt.

I usually get this error after I format a device into a FAT filesystem, it works fine at first then suddenly read-only filesystem.

FeyFre · 01-28-2013, 10:18 AM

@varunb, do you solved your problem?
There is exits another reason for this error: exhausting of inodes. Check it up.

varunb · 01-28-2013, 11:45 PM

Quote:

Originally Posted by FeyFre

@varunb, do you solved your problem?
There is exits another reason for this error: exhausting of inodes. Check it up.

hey still in observation. .
i had got the same error again, did restart and seems working fine.

But how do you check the exhausting of inodes??? any command ???

chrism01 · 01-29-2013, 01:31 AM

inodes

Code:

df -i

http://linux.die.net/man/1/df