From tomathie@u.washington.edu Mon Jul 16 11:54:25 2001
Received: from jason05.u.washington.edu (jason05.u.washington.edu [140.142.8.54])
	by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GIsK038158
	for <linux@lists.u.washington.edu>; Mon, 16 Jul 2001 11:54:21 -0700
Received: from dante50.u.washington.edu (tomathie@dante50.u.washington.edu [140.142.15.100])
	by jason05.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GIsJA44430
	for <linux@u.washington.edu>; Mon, 16 Jul 2001 11:54:20 -0700
Received: from localhost (tomathie@localhost)
	by dante50.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f6GIsJo145208
	for <linux@u.washington.edu>; Mon, 16 Jul 2001 11:54:19 -0700
Date: Mon, 16 Jul 2001 11:54:19 -0700 (PDT)
From: Thomas Anderl <tomathie@u.washington.edu>
To: <linux@u.washington.edu>
Subject: xfs dead but subsys locked
Message-ID: <Pine.A41.4.33.0107161054130.135962-100000@dante50.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Hi All,

I'm running RH6.2 and up until this morning, it's been running just fine.
I have it start into X automatically, so I usually turn the machine on,
and come back after a couple of minutes to the X login screen.  This time,
however, when I came back, it gave me a console login.

running startx gives:

<errors>
(many SVGA messages that I'm pretty sure are just info)
_FontTransSocketUNIXConnect: Can't connect: errno = 111
failed to set default font path 'unix/:-1;
Fatal server error:
could not open default font 'fixed'

When reporting a problem related to a server crash, please send the full
server output, not just the last messages

X connection to :0.0 broken (explicit kill or server shutdown)
</errors>


So I look this up, and it looks like the problem is probably with xfs.  I
run:
"/etc/rc.d/init.d/xfs status"
and it tells me:
"xfs dead but subsys locked"

Some solutions I saw out on the internet that I tried but didn't
work were:

(1) rm /var/lock/subsys/xfs

(2) change the port that xfs is using along with the port that X uses to
connect to xfs.

(3) make sure there is space on both /tmp and /.  Well, /tmp is on the
same partition as / and df -m gives:
Filesystem	1M-blocks	Used 	Available 	Use% Mounted on
/dev/sda1	     4918       1300         3368        28% /
/dev/sda6	     2602         90         2380         4% /kerry

so I don't think that space is an issue.



(4) try starting xfs from the command line to see what happens.

# xfs
eth0: Promiscuous mode enabled.
# ps -aux | grep xfs
#

So this is what I've tried, with no luck.  One thing that I don't think is
related, but I'm not sure:  /log/messages contains:

rpc.lockd: lockdsvc: Connection refused
nfslock: rpc.lockd startup failed

and a little later...

portmap: RPC call returned error 111


Any ideas how to get X to start again?

Thanks,

Tom

-------------------------------------------------------------------------------

.