Check your various system logs.  You may have a bad filesystem or 
failing hard drive.  When the OS detects problems, it has a tendency to 
auto-remount read-only.

Cheers,
Mark

Rachid Ayad wrote:
> On Sat, 2 Aug 2008, Akemi Yagi wrote:
> 
>> On Sat, Aug 2, 2008 at 3:00 PM, Rachid Ayad <[log in to unmask]> wrote:
>>> On Sat, 2 Aug 2008, Brian Andrus wrote:
>>
>>>>> On Sat, 2 Aug 2008, Brian Andrus wrote:
>>>>>
>>>>>> try unmounting and remounting /tmp
>>>>>>
>>>>>> umount /tmp
>>>>>> mount /tmp
>>>>>
>>>>>  You mean umount /scratch
>>>>>
>>>>>> check in your /etc/fstab to see if it is set for read-only.
>>>>>
>>>>>  In /etc/fstab  I have:
>>>>>
>>>>> /dev/hdb1           /scratch            ext3    rw,auto,user    0 0
>>
>> You can remount with read/write permissions like:
>>
>> mount -o rw,remount /dev/hdb1 /scratch
> 
>  Hello Akemi, I think there is a prolem with changin permission, 
> owner,groups in SL: I was doing this all my life with other linux-like 
> systems and I never had any problem in particular if I was doing from 
> root. I followed your procedure by unmounting, mounting, and remounting 
> but it works for few minutes and later my mounted path (HD) looses its 
> rw option and becomes only read-only. I tried it several times because I 
> checked that now chown command shows that /scratch is read-only, so I 
> unmouted, mounted, and remount as you said above, then run "chown" it 
> works for a while(but before it immediately says read-only) and then 
> messages saying /scratch file system are read-only. The same thing 
> happened when we tried to let files from a user seen from another user 
> by running: "chmod -R g+rw directory" from root but after doing this the 
> second user still do not see the files even if the two users have the 
> group.
> 
>  Regards, rachid .
> 
>>
>> Akemi
>>
>