Coda File System

Re: SpoolVMLogRecord - no space left in volume

From: Ed Kuo <edkcc_at_yahoo.com>
Date: Mon, 25 Jun 2001 18:06:03 -0700 (PDT)
Hello all

These problems solved after I upgrade to 5.3.15. 
I think it maybe compatibility problem, for 5.3.14 is
not supposed to be installed on Redhat 7.x. Now it
works pretty well.
Thanks Jan and Shafeeq

Ed

--- Shafeeq Sinnamohideen <shafeeq_at_cs.cmu.edu> wrote:
> 
> 
> On Tue, 19 Jun 2001, Ed Kuo wrote:
> 
> > [root_at_cluster1 /coda]# volutil -h cluster1
> setlogparms
> > 1000003 reson 4 logsize 16384
> > V_BindToServer: binding to host cluster1
> > Set Log parameters
> > [root_at_cluster1 /coda]# volutil -h cluster3
> setlogparms
> > 3000002 reson 4 logsize 16384
> > V_BindToServer: binding to host cluster3
> > Set Log parameters
> > [root_at_cluster1 /coda]#
> 
> This is correct, the log parameters (and most things
> set with volutil) are
> poperties of a _replica_, not the entire replicated
> volume.
> 
> > Actually, i did it and venus crashed, then I
> restart
> > venus with the following message shown:
> 
> This seem suspicious, but there shouldn't be a
> connection. Nothing
> simple left to do but start with -init once.
> 
> Shafeeq
> 
> 


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
Received on 2001-06-25 21:07:30