Coda File System

Re: create volume returns 103

From: lou <lou_at_0xffff.org>
Date: Fri, 18 Apr 2003 15:39:14 +0100
In some email I received from Jan Harkes <jaharkes_at_cs.cmu.edu> on Fri, 18 Apr 2003
10:23:20 -0400, wrote:

> On Fri, Apr 18, 2003 at 03:04:18PM +0100, lou wrote:
> > I'm having a problems with my coda server. It's a linux box, 
> > with 500M RVM data and 30M log partition.
> > when i issue 
> > createvol_rep ROOTVOLUME E0000100 /volumes/vicepa
> ...
> > 14:03:10 VGetPartition Couldn't find partition 0
> > 14:03:10 VCreateVolume: Cannot find partition 0. Bailing out.
> 
> It looks like the server has a problem finding the /volumes/vicepa
> partition. Was /vice/db/vicetab changed since the server was started? If
> so you probably need to restart the server.

Nope. Evertyhing in vicetab looks alright;
-> host1   /volumes/vicepa   ftree   width=256,depth=3

> Are there any messages around the top of SrvLog indicating that the
> server actually could or could not find the partitions specified in the
> vicetab file?

vicepa is a different partition mounted onto /volumes/vicepa same with /vice.
or
-> /dev/hda11 on /vice type reiserfs (rw)
-> /dev/hda12 on /volumes/vicepa type reiserfs (rw)




I dont think so, here's the snip:

14:32:07 RvmType is Rvm
14:32:07 Main process doing a LWP_Init()
14:32:07 Main thread just did a RVM_SET_THREAD_DATA
14:32:07 Setting Rvm Truncate threshhold to 5.
Partition /volumes/vicepa: inodes in use: 0, total: 16777216.
14:32:34 Partition /volumes/vicepa: 2441768K available (minfree=0%), 2408928K free.
>> that looks positive enough.

14:32:34 The server (pid 2867) can be controlled using volutil commands
14:32:34 "volutil -help" will give you a list of these commands
14:32:34 If desperate,
                "kill -SIGWINCH 2867" will increase debugging level
14:32:34        "kill -SIGUSR2 2867" will set debugging level to zero
14:32:34        "kill -9 2867" will kill a runaway server
14:32:34 VCheckVLDB:  bad VLDB!
14:32:34 VInitVolPackage: no VLDB! Please create a new one.
14:32:34 Vice file system salvager, version 3.0.
14:32:34 SanityCheckFreeLists: Checking RVM Vnode Free lists.
14:32:34 DestroyBadVolumes: Checking for destroyed volumes.
14:32:34 Salvaging file system partition /volumes/vicepa
14:32:34 Force salvage of all volumes on this partition
14:32:34 Scanning inodes in directory /volumes/vicepa...
14:32:35 SalvageFileSys completed on /volumes/vicepa
>> same here.

14:32:35 Attached 0 volumes; 0 volumes not attached
lqman: Creating LockQueue Manager.....LockQueue Manager starting .....
14:32:35 LockQueue Manager just did a rvmlib_set_thread_data() done
14:32:35 CallBackCheckLWP just did a rvmlib_set_thread_data()
14:32:35 CheckLWP just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 0 just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 1 just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 2 just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 3 just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 4 just did a rvmlib_set_thread_data()
14:32:35 ServerLWP 5 just did a rvmlib_set_thread_data()
14:32:35 ResLWP-0 just did a rvmlib_set_thread_data()
14:32:35 ResLWP-1 just did a rvmlib_set_thread_data()
14:32:35 VolUtilLWP 0 just did a rvmlib_set_thread_data()
14:32:35 VolUtilLWP 1 just did a rvmlib_set_thread_data()
14:32:35 Starting SmonDaemon timer
14:32:35 File Server started Fri Apr 18 14:32:35 2003

Thanks for the input Jan! Any other ideas?

cheers

-- 

Lou Kamenov	AEYE R&D 	lou.kamenov_at_aeye.net	
FreeBSD BGUG	http://www.freebsd-bg.org	lou@FreeBSD-bg.org	
Secureroot UK	http://secureroot.org.uk	phayze@secureroot.org.uk
Key Fingerprint - 936F F64A AD50 2D27 07E7  6629 F493 95AE A297 084A
One advantage of talking to yourself is that you know at least
somebody's listening. - Franklin P. Jones 
Received on 2003-04-18 10:41:06