You don't mention what hardware and disk controller you are running. I can tell you if its HP G1 hardware with CCISS 200/200i - you may want to check the firmware and possibly linux CCISS module.
I wont go into more details unless that is the case and you are running HP hardware. You can also try burn testing you disks, i use a tool called vdt by alex botao, there are probably others you can use. Best of luck -ilya ________________________________________ From: rhelv5-list-boun...@redhat.com [rhelv5-list-boun...@redhat.com] On Behalf Of Hugh Brown [hbr...@divms.uiowa.edu] Sent: Wednesday, October 05, 2011 10:10 AM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] read-only file system errors: what is causing them and how to avoid them? 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 _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list rhelv5-list@redhat.com https://www.redhat.com/mailman/listinfo/rhelv5-list
