Excerpts from internet.info-afs: 10-Sep-96 afsd: Can't mount AFS on /a..
by Peo [EMAIL PROTECTED]
> *** Lots of messages ***
> afsd: Forking trunc-cache daemon.
> afsd: Mounting the AFS root on '/afs', flags: 4.
> afsd: Can't mount AFS on /afs(16)
There's a helpful clue hidden in the last message. The number inside the
parens is actually the "errno" value set by the failing "mount()" call.
On a Solaris machine, 16 translates to "device busy":
[~] translate_et 16
16 ().16 = Device busy
[~] grep 16 /usr/include/sys/errno.h
#define EBUSY 16 /* Mount device busy */
The errno values don't always match across different OSs, so you'll want
to check on your SunOS 4.1.4 machine to be sure of the meaning.
You get a "device busy" error when the /afs directory is in use already.
Use the "mount" command to see if someone has already started AFS. Or
perhaps someone NFS mounted /afs while you weren't looking. Also be sure
that no one has their current working directory set to /afs when you
start it up. That's all I can think of off the top of my head.
Joe Jackson.
