"Read-only file system" but it's rw

jovie · 06-16-2006, 07:22 AM

Hi

Can anyone explain why my system cliams /data is read only when half an hour ago I could write to it and mount say's it's rw?

It won't umount either, dievice busy even after fuesr -mk /data.

Thanks

Code:

[root@galaxy /data]# mkdir junk
mkdir: cannot create directory `junk': Read-only file system
[root@galaxy /data]# mount
/dev/hda2 on / type ext3 (rw)
/dev/proc on /proc type proc (rw)
/dev/sys on /sys type sysfs (rw)
/dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda1 on /boot type ext3 (rw)
/dev/shm on /dev/shm type tmpfs (rw)
/dev/hda3 on /home type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
automount(pid1988) on /misc type autofs (rw,fd=4,pgrp=1988,minproto=2,maxproto=4)
automount(pid2030) on /net type autofs (rw,fd=4,pgrp=2030,minproto=2,maxproto=4)
/dev/sda1 on /data type ext3 (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
[root@galaxy /data]#

[root@galaxy /]# fuser -mk /data
[root@galaxy /]# umount /data
umount: /data: device is busy
umount: /data: device is busy

bigrigdriver · 06-16-2006, 08:15 AM

According to this "[root@galaxy /data]#", you are in the /data directory when trying to umount. You are keeping it busy. Cd out of /data, then try to umount.

As for writing to /data, check the user's permission to write. The partition can be mounted rw, but if the user doesn't have write permission, he can't write to /data.

jovie · 06-16-2006, 09:15 AM

Thanks for responding

Quote:

Originally Posted by bigrigdriver

According to this "[root@galaxy /data]#", you are in the /data directory when trying to umount.

Nope I was in / when I tried umount. I was in /data when I tried (as root) to write to it with mkdir as an example of the problem. 'mount' say's it's still rw and I can't umount so I can't re-mount it which would solve the problem if not the cause.

This is happening ~twice a day and the only way I have to clear it is a reboot. I'm going to leave the next occurence to see if some process is making it temporarily read-only.

Any other ideas?