On Sun, 3 Aug 2008, Billy Crook wrote:

> This goes without saying, but you may want to compare your backups to
> what you have on disk, and restore files where necessary if the data
> is at all important.  If it's completely disposable, you might
> consider a script to umount, reformat, and remount the volume every so
> often

  As I said before, fsck fixed the bad sectors but I do not know if the 
content of the memory is well restored. I am saying this because at the 
end of fsck the system told me that the content of the bad sectors are 
saved in /scratch/lost+found/ with files labeled with the sector number 
like: /scratch/lost+found/#5914818 , so are these files are really a 
backup of the corrupted memory? are there really good to restore? and how 
we can restore them from /scratch/lost+found .

  Regards, rachid.

>
> On Sun, Aug 3, 2008 at 20:08, Rachid Ayad <[log in to unmask]> wrote:
>> On Sun, 3 Aug 2008, Akemi Yagi wrote:
>>
>>> On Sun, Aug 3, 2008 at 1:57 PM, Mark Stodola <[log in to unmask]>
>>> wrote:
>>>>
>>>> Rachid Ayad wrote:
>>>>>
>>>>> On Sat, 2 Aug 2008, Akemi Yagi wrote:
>>>>>
>>>>>  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 .
>>>
>>>> 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.
>>
>>  Yes it was the filesystem: many bad sectors in the HD like:
>> ***********
>> Error reading block 10289160 (Attempt to read block from filesystem
>> resulted in short read) while doing inode scan.  Ignore error<y>? yes
>>
>> Force rewrite<y>? yes
>> ***********
>>
>>  after fixing them all with fsck, chown command worked well. So it was
>> really the auto-mount in read-only state.
>>
>>  Thank you, Rachid.
>>
>>
>>>>
>>>> Cheers,
>>>> Mark
>>>
>>> Yes, that description indicates some problem causing the filesystem to
>>> go read-only.  Umount the troubled filesystem and try running fsck on
>>> it.
>>>
>>> Akemi
>>>
>>> Akemi
>>>
>>
>