Thanks for your reply. Lots of things there! I have merged my answers with your questions below although haven't tried everything yet. Perhaps my answers might give a few more clues to the problem though.
Is /afs available on other AFS clients? That rules out some possibilities.
Yes, on some of them. 50% have this problem though.
I'd go to a well-behaved client, cd /afs, fs flushv, cd /afs and see if /afs
is still available on that client.
Yes, tried this and /afs was still available.
I'd also be interested in
vos exa root.afs vos exa root.afs.readonly
vos exa root.afs gave (on well behaved client):
root.afs 536870915 RW 4 K On-line rsl155 /vicepa RWrite 536870915 ROnly 536870916 Backup 0 MaxQuota 5000 K Creation Wed Aug 1 21:24:27 2001 Last Update Wed Aug 1 22:23:23 2001 0 accesses in the past day (i.e., vnode references)
RWrite: 536870915 ROnly: 536870916
number of sites -> 3
server rsl155 partition /vicepa RW Site
server rsl156 partition /vicepa RO Site
server rsl59 partition /vicepa RO Sitevos exa root.afs.readonly gace:
root.afs.readonly 536870916 RO 4 K On-line rsl156 /vicepa RWrite 536870915 ROnly 0 Backup 0 MaxQuota 5000 K Creation Tue Dec 9 13:48:39 2003 Last Update Tue Dec 9 13:48:39 2003 761 accesses in the past day (i.e., vnode references)
root.afs.readonly 536870916 RO 4 K On-line rsl59 /vicepa RWrite 536870915 ROnly 0 Backup 0 MaxQuota 5000 K Creation Tue Dec 9 13:48:39 2003 Last Update Tue Dec 9 13:48:39 2003 1576 accesses in the past day (i.e., vnode references)
RWrite: 536870915 ROnly: 536870916
number of sites -> 3
server rsl155 partition /vicepa RW Site
server rsl156 partition /vicepa RO Site
server rsl59 partition /vicepa RO Site
to see if the root.afs and root.afs.readonly volumes are on line, though if /afs is available on other clients the output is moot.
rxdebug <hostname> 7001 will give you some info about activity on the AFS
client's callback port
On a working client:
rsl55:/afs/.uk.baplc.com# rxdebug rsl55 7001 Trying 167.156.154.55 (port 7001): Free packets: 130, packet reclaims: 0, calls: 101338, used FDs: 64 not waiting for packets. 0 calls waiting for a thread 1 threads are idle Connection from host 167.156.154.55, port 7000, Cuid 9915c0ac/1817cfe8 serial 128760, natMTU 1444, flags pktCksum, security index 2, client conn rxkad: level clear, flags pktCksum Received 271944 bytes in 2518 packets Sent 180088696 bytes in 128706 packets call 0: # 2518, state dally, mode: receiving, flags: receive_done call 1: # 0, state not initialized call 2: # 0, state not initialized call 3: # 0, state not initialized Done.
On a broekn client:
rsl56:/# rxdebug rsl56 7001 Trying 167.156.154.56 (port 7001): Free packets: 130, packet reclaims: 0, calls: 79437, used FDs: 64 not waiting for packets. 0 calls waiting for a thread 1 threads are idle Done.
df to see if /afs still appears in the output
/dev/logsarc 9469952 6327480 34% 244 1% /logs/archive AFS df: /afs: No such file or directory
You don't mention the debug level of your fileserver. kill -HUP <PID of
fileserver> will set debug levels to 0 (default). kill -TSTP bumps one
level per kill -- to levels 1, 5, 25 -- some experiments I've done (but not
yet repeated) indicate some performance impact at debug level 25 but none at
levels 1 or 5. Not sure if anything would show up so might try this late in
the game.
Create a new volume on the fileserver, mount it, make sure it's accessible.
Check the afsd startup arguments and make sure that
[-rootvol <name of AFS root volume>] and [-mountdir <mount location>]
don't change the default root volume (root.afs) or default root directory (/afs). Unlikely but worth checking pro forma.
afsmonitor -cm <hostname> -fs <hostname> -freq 5
will tell you if there's any activity on the cache manager/fs ; you're probably not interested in -fs if the fileserver is behaving orrectly. -freq 5 specifies 5 second update interval instead of the 60 sec default. Your mileage may vary. I like to see numbers change more frequently than every minute.
When was the client last confirmed working correctly?
It was working until 10th April.
Kim
================================= Kim (Dexter) Kimball CCRE, Inc. afsinfo at ccre dot com
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of J S > Sent: Tuesday, April 13, 2004 4:53 AM > To: [EMAIL PROTECTED] > Subject: [OpenAFS] /afs does not exist > > > Hi, > > I'm having problems getting in to the /afs directory on an AIX > box and I'm > not sure how to fix it: > > # cd /afs > ksh: /afs: not found. > > This has been running fine until now though. The processes are still > running: > > rsl57:/usr/afs/local# ps -ef | grep afs > root 17314 40486 0 11 Apr - 0:00 /usr/afs/bin/fileserver > root 17686 40486 0 11 Apr - 0:00 /usr/afs/bin/volserver > root 20134 1 0 08 May - 17:24 /usr/vice/etc/afsd > -stat 2800 > -dcache 2400 -daemons 5 -volumes 128 > root 20384 1 0 08 May - 17:23 /usr/vice/etc/afsd > -stat 2800 > -dcache 2400 -daemons 5 -volumes 128 > .. > .. > root 40486 1 0 11 Apr - 0:00 /usr/afs/bin/bosserver > > And the logs look normal. I can ping the AFS server also. > > Is there anything else I can try? > > Thanks for any help. > > JS. > > _________________________________________________________________ > It's fast, it's easy and it's free. Get MSN Messenger today! > http://www.msn.co.uk/messenger > > _______________________________________________ > OpenAFS-info mailing list > [EMAIL PROTECTED] > https://lists.openafs.org/mailman/listinfo/openafs-info >
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
_______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
