On 10/05/2011 02:25 PM, Mirko Vukovic wrote:
On Wed, Oct 5, 2011 at 10:10 AM, Hugh Brown<hbr...@divms.uiowa.edu> wrote:
On 10/05/2011 08:54 AM, Mirko Vukovic wrote:
Hello,
I wrote a script to clean up about 80GB of data from one disk and replace
the deleted data by their archives. The archives were created ahead of
time
and stored on a second disk.
The script starts OK, but after a while, I get errors due to `read-only
file
system'.
I read that I can reset the file access by remounting the file system, and
that works. I can then restart the script, but I get the error again
after
a while. What am I doing to cause this error?
The script, in pseudocode:
for dir in `...'
do
rm -f $dir
cp $archive (from other disk) $dir
done
Should I put a pause statement, or do something else?
Thank you,
Mirko
If a file system goes read-only, it's usually because of read/write errors
(i.e. a failing disk).
Check your smartd output and /var/log/messages for errors.
Hugh
Thanks to all.
I have updated the /etc/smartd.conf file and restarted smartd
I also did the long and short tests using smartlcd, but these reported no
errors.
I'll keep watching
I'd also force a run of fsck against the filesystem.
Hugh
_______________________________________________
rhelv5-list mailing list
rhelv5-list@redhat.com
https://www.redhat.com/mailman/listinfo/rhelv5-list
