Date:  Sat, 03 Mar 2007 13:29:46 -0500
From:  Jon McCauley <jmccauley (at mark) ontarioweb.ca>
Subject:  [coba-e:08981] Re: /var/lock/subsys/proftpd': Read-only file system
To:  coba-e (at mark) bluequartz.org
Message-Id:  <45E9BE9A.7030904 (at mark) ontarioweb.ca>
In-Reply-To:  <1486c6440703030816q21795bc0xf2414070dd6ec3f3 (at mark) mail.gmail.com>
References:  <057501c75d2a$50d31990$0601a8c0 (at mark) systemax>	 <45E98C84.8060400 (at mark) ontarioweb.ca> <1486c6440703030816q21795bc0xf2414070dd6ec3f3 (at mark) mail.gmail.com>
X-Mail-Count: 08981



Adam Crews wrote:
> Run the command "mount"  without any arguments and look for a "ro"
> (read only) file system.
>
> If you find any then run dmesg, or look in /var/log/messages for clues
> to why the filesystem was marked read only.
>
> If the kernel detects an error on the file system, it will sometimes
> mark it as read-only to prevent damage to the files.  This could
> indicate a failing disk, or dirty file system.  dmesg or
> /var/log/messages should help determine what is happening.
>
> -Adam
>
>>
>>
>
Hi Adam, thanks for the response...

[root@ns1 ~]# mount
/dev/md1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/md0 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/md4 on /home type ext3 (rw,usrquota,grpquota)
/dev/md2 on /tmp type ext3 (rw)
/dev/md3 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
/proc on /var/named/chroot/proc type none (rw,bind)

[root@ns1~]# dmesg

received "many"
EXT3-fs error (device md3) in start_transaction: Journal has aborted


[root@ns1 ~]# tail -f /var/log/messages
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 216.109.116.20#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 66.218.71.205#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 216.109.116.20#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 66.218.71.205#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 216.109.116.20#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 66.218.71.205#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 216.109.116.20#53
Mar  2 15:15:47 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 66.218.71.205#53
Mar  2 15:15:48 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 216.109.116.20#53
Mar  2 15:15:48 ns1 named[1903]: lame server resolving 
'sherriandsamantha.com' (in 'sherriandsamantha.com'?): 66.218.71.205#53


The logs sure do not help any here ;(

Jon