On Tue, 2007-05-29 at 10:24 -0600, Tim Donnelly wrote: > I am using Suse 10.2 on two different machines. One is a new Dell > Poweredge 2970, the other is an older (2002) "no-name" server.
I have the same problem with two machines, one a dual core x86_64 and a AMD XP2000 ... self built together and working 2 and 5 years respectively. > Both have experienced a strange and severe problem since I installed > Suse. i had it with SuSE 9.3, 10.0, 10.1 (Boxed Novell purchased version) and now with OpenSUSE 10.2 > > Basically the file system is put into a read-only state. This I noticed only now with OpenSUSE 10.2, the others just locked up solid. > While the OS and all apps are still running and I can log in a view > files/logs etc. nothing can write to the disks. I could only log in ssh from another machine. > Obviously this causes all kinds of problems. The only way to get the > filesystem into a more interactive state is a hard reboot. Same here > > The first two times this occurred, there were messages in > the /var/log/messages file relating to megasas, I did not see it at all. The x86_64 system has SATA, and the other IDE > however as soon as the system was restarted, these warnings > disappeared. Until some days later perhaps. I have excessive problems with some versions of Evolution and the newest OpenOffice 2.2 running high disk access, then no access to the system is possible; the disks are in constant access (LED permanently on). Just the M$ reset trick works. :-( Al -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
