Coda File System

Re: NetBSD 1.6 hanging on venus startup

From: Brett Lymn <blymn_at_baesystems.com.au>
Date: Wed, 1 Jan 2003 18:47:04 +1030
On Tue, Dec 31, 2002 at 02:52:52PM -0500, Jan Harkes wrote:
> 
> The code in venus that handles mounting on *BSD is very different. It
> first tries to unmount any existing tree and then does a mount syscall,
> I guess it isn't expecting upcalls during this operation.
>

This is probably related, possibly because coda is getting stuck in
the mount syscall but the output from df is wrong at this point too -
it only "comes good" when you use the coda file system (do a ls or cd
into it) only then does the output look right.  Here is a sample:

[blymn_at_siren] df
Filesystem  512-blocks     Used     Avail Capacity  Mounted on
/dev/wd0a     60622934 35869196  21722590    62%    /
procfs               8        8         0   100%    /proc
                     0        0         0   100%    
[blymn_at_siren] ls /coda/working
....stuff....

[blymn_at_siren] df 
Filesystem  512-blocks     Used     Avail Capacity  Mounted on
/dev/wd0a     60622934 35869198  21722588    62%    /
procfs               8        8         0   100%    /proc
CODA            320000     2416    251696     0%    /coda

 
> So either we have to figure out why getNewVnode is called, or use the
> trick that is used for Linux and fork off a child process to perform the
> mount syscall.
> 

I will see if I can workout why getNewVnode is called.

-- 
Brett Lymn
Received on 2003-01-01 03:19:09