[OpenAFS] "vos create" problem

Mitch Collinsworth mitch@ccmr.cornell.edu
Mon, 2 Apr 2001 07:09:48 -0400 (EDT)

"Something bad" is happening here.  At the moment you ran these commands,
salvager was running, which isn't necessarily bad in itself.  Salvager is
to volumes like fsck is to partitions.  It's just cleaning up the mess
that was left when fileserver died unexpectedly.  Once salvager finishes
bos will fire up fileserver and volserver and then you _should_ be in

However...  Your status command suggests the servers are probably failing
to run and dumping core (49 proc starts).  You need to find out why this
is.  Check the contents of your log files for any clues left there.


On Mon, 2 Apr 2001, Sergei Naumov wrote:

> Hi!
> I am installing OpenAFS 1.0.3 on Sun/Solaris 2.7. Going through the steps in
> "Quick
> Beginnings" I came to the step that creates the AFS volume but it yells at me
> with this:
>     # ./bos status perun fs -long -noauth
>     Instance fs, (type is fs) has core file, currently running normally.
>     Auxiliary status is: salvaging file system.
>     Process last started at Mon Apr  2 14:10:44 2001 (49 proc starts)
>     Last exit at Mon Apr  2 14:10:44 2001
>     Last error exit at Mon Apr  2 14:10:44 2001, by file, due to signal 12
>     Command 1 is '/usr/afs/bin/fileserver'
>     Command 2 is '/usr/afs/bin/volserver'
>     Command 3 is '/usr/afs/bin/salvager'
>     # ./vos create perun /vicepa root.afs -cell r-style.donpac.ru -noauth
>     Could not fetch the list of partitions from the server
>     Possible communication failure
>     Possible communication failure
>     #
> I thought it might be a DNS thing and tried a fully qualified name for the
> server and also an
> IP number. It still says the same thing.
> How do I deal with this situation?
> Thanks much,
> 		Sergei
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo.cgi/openafs-info