John, That's not a problem of the file system. I use xfs with myth and I have not had any problems. Two lockup a day something is not right. Just do the basic things.
1. Look at hardware problems. Some are easy to find some are not :-( Load the installation opensuse dvd and run the memory test for many hours. Be sure you have not errors there. Memory errors will produce those problems and the memory test works very well to find them. 2. kcontrol/KDE components/session manger/Start with an empty session. Then use the system and see what happen 3. If it does not do it, just leave like that and stop or remove zen beagle This 3 is unlikely to cause those type of problems. 4. You can add in the kicker the "RUnaway Process Catcher" It is a neat tool, however those process usually do not lock the system, a faulty memory will do it. Good luck -=terry(Denver)=- On Sat, 2007-04-21 at 12:45 -0500, John Pierce wrote: > > > > I would not attribute these symptoms to XFS. XFS is a mature, stable > > file system, at least as much as any other available in SuSE Linux / > > openSUSE. > > > > If your system is unstable, I'd diagnose the problem, probably > > hardware-related in this case, before a protracted file system > > conversion that is unlikely to yield any improvement. > > > > > > If you can establish a login via ssh or telnet from another computer > > (only use telnet if the connection is via network link that's behind a > > firewall or otherwise isolated from the Internet) in advance of the > > symptom, then when the hang occurs you may still be able to run some > > commands such as ps, top or one of the various monitoring commands. The > > first thing to look for is processes hung in a 'D' wait state (using > > ps). This can sometimes be the result of software problems (disk or > > file system drive bugs) but when it occurs frequently is probably the > > sign of a problem with a disk drive, controller or bus interface > > component. > > > I have seen a lot of traffic on other lists concerning the xfs file > system and random lockups caused by it. As posted earlier, I have > already converted the /home, /var, and /tmp partitions to ext3 and the > problems seem to be less frequent now. As to frequency, I was have at > least 2 lock ups per day on average. > > During these lock ups I had tried to ssh in to the machine but always > got a 'no route to host' response from ssh. > > Only powering off the machine would bring it back. I have not seen > anything in the logs to indicate a problem. > > Thanks for your input. I will continue to try to get into the machine > during any lock up though. > -- > John > Registered Linux User 263680, get counted at > http://counter.li.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
