(Illustration by Gaich Muramatsu)
On Mon, Mar 07, 2005 at 10:16:47AM -0300, Gabriel B. wrote: > On Sat, 5 Mar 2005 00:20:48 +0100 (CET), Michael Tautschnig > <michael.tautschnig_at_zt-consulting.com> wrote: > > > also, when i do an ls in /coda on the client, it take ages, and then i > > get: > > > bossnes:/# ls -la /coda/camboinha.servers > > > lrw-r--r-- 1 root nogroup 20 Mar 4 18:31 > > > /coda/camboinha.servers -> #@camboinha.servers > > > bossnes:/# cd /coda/ > > Probably your root-volume is not set up correctly - what does venus tell > > you (/var/log/coda/venus.{log|err})? > > tail of log: > 10:10:49 ResLWP-1 just did a rvmlib_set_thread_data() > 10:10:49 VolUtilLWP 0 just did a rvmlib_set_thread_data() > 10:10:49 VolUtilLWP 1 just did a rvmlib_set_thread_data() > 10:10:49 Starting SmonDaemon timer > 10:10:49 File Server started Mon Mar 7 10:10:49 2005 > Err is empy. > > some comands: > In this case the head of the log might be more interesting. My guess is that the server didn't find the /vicepa partition in /vice/db/vicetab and as a result we failed to create the initial root volume. > # volutil getvolumelist > V_BindToServer: binding to host camboinha > GetVolumeList finished successfully That's a good indication that there are no known partitions on the server, otherwise it would have looked more like V_BindToServer: binding to host telemann P/vicepa Htelemann T12afa7c F12a72f0 W/.0 I1000001 H1 P/vicepa m0 M0 U4 W1000001 C415af94e D415af94e B0 A51 GetVolumeList finished successfully Where the first line indicates that there is a partition /vicepa and the second line show that we have a writeable volume replica named '/.0' (which is the first replica of a replicated volume named '/') All the other info on these lines are things like how many block are in available/inuse, if there is a quota set and the last modification timestamp etc. JanReceived on 2005-03-08 07:46:37