Coda File System

Re: /coda has realm as symlink

From: Jerry Amundson <jerry_at_pbs.com>
Date: Sat, 15 Oct 2005 23:55:54 -0500
On Sat October 15 2005 21:16, Jerry Amundson wrote:
> On Sat October 15 2005 15:53, Jerry Amundson wrote:
> > Not sure where to go with this. Maybe caused by servers having two NIC's,
> > or running venus on the same host as server (yes, I've seen the advice
> > against this - can't really help it)... two strikes and I'm out?
>
> (theorizing here...)
> I may have thrown strike three myself when I created the volume without a
> preceding "/" in the name?
>
> Either way, I'm re-initing (for the second time), this time with a "/" to
> start the volume name.

Better now...
took server names out of "localhost" line in /etc/hosts - previously I just 
added ipaddress setting in server.conf but this prevents vice-setup from 
running createvol_rep successfully. This time createvol_rep (within 
vice-setup) created a perfectly functioning "/" volume.
It seems, then, that I could have correctly continued the setup manually had I 
entered the first volume as "/" (or "/something"?).
RFE : Syntax check at creation that volume names start with "/" (if indeed, it 
is required...).

Noticed along the way...
"norton" complains about "server" resolving to localhost, and to change the 
ipaddress value in server.conf, even though server.conf has already been 
modified. I.e. norton seems to ignore server.conf, or at least the ipaddress 
setting.

Lastly, the search function of bugs on the web-site is broken (logged in as 
guest).
error:   too many arguments 
at /usr/share/request-tracker3.4/lib/RT/Tickets_Overlay.pm line 1299

jerry

> > Wroot.0 I1000001 H1 P/var/vicepa m0 M0 U2 W1000001 C4351577d D4351577d B0
> > Wroot I2000001 H2 P/vicepa m0 M0 U2 W2000001 C43515a55 D43515a55 B0 A0
> >
> >
> > [domain name munged]
> >
> > [root_at_aspen ~]# ls -l /coda
> > total 1
> > lrw-r--r--  1 root nfsnobody 14 Oct 15 14:47 example.com -> #@example.com
> > [root_at_aspen ~]# ctokens
> > Tokens held by the Cache Manager for root:
> >     @example.com
> >         Coda user id:    646
> >         Expiration time: Sun Oct 16 15:47:29 2005
> >
> > [root_at_aspen ~]# cat /usr/coda/etc/console
> >
> > Date: Sat 10/15/2005
> >
> > 14:47:03 Coda Venus, version 6.0.12
> > 14:47:03 /usr/coda/LOG size is 1094612 bytes
> > 14:47:03 /usr/coda/DATA size is 4378448 bytes
> > 14:47:03 Initializing RVM data...
> > 14:47:03 ...done
> > 14:47:03 Loading RVM data
> > 14:47:03 Starting RealmDB scan
> > 14:47:03        Found 1 realms
> > 14:47:03 starting VDB scan
> > 14:47:03        0 volume replicas
> > 14:47:03        0 replicated volumes
> > 14:47:03        0 CML entries allocated
> > 14:47:03        0 CML entries on free-list
> > 14:47:03 starting FSDB scan (1666, 40000) (25, 75, 4)
> > 14:47:03        0 cache files in table (0 blocks)
> > 14:47:03        1666 cache files on free-list
> > 14:47:04 starting HDB scan
> > 14:47:04        0 hdb entries in table
> > 14:47:04        0 hdb entries on free-list
> > 14:47:04 Initial LRDB allocation
> > 14:47:04 Mounting root volume...
> > 14:47:04 Venus starting...
> > 14:47:04 /coda now mounted.
> > ***LWP (0x846ce00): Select returns error: 4
> >
> > 14:47:14 worker::main Got a bogus opcode 36
> > An address in realm 'example.com' resolved to unusable address
> > '127.0.0.1', ignoring it
> > 14:47:29 Resolved realm 'example.com'
> >
> > Servers (oak and aspen) look OK :
> >
> > [root_at_aspen db]# getvolinfo aspen root
> > RPC2 connection to aspen:2432 successful.
> > Returned volume information for root
> >         VolumeId 7f000000
> >         Replicated volume (type 3)
> >
> >         Type0 id 0
> >         Type1 id 0
> >         Type2 id 0
> >         Type3 id 7f000000
> >         Type4 id 0
> >
> >         ServerCount 2
> >         Replica0 id 01000001, Server0 10.1.110.5
> >         Replica1 id 02000001, Server1 10.1.110.6
> >         Replica2 id 00000000, Server2 0.0.0.0
> >         Replica3 id 00000000, Server3 0.0.0.0
> >         Replica4 id 00000000, Server4 0.0.0.0
> >         Replica5 id 00000000, Server5 0.0.0.0
> >         Replica6 id 00000000, Server6 0.0.0.0
> >         Replica7 id 00000000, Server7 0.0.0.0
> >
> >         VSGAddr 0
> >
> > [root_at_oak ~]# getvolinfo aspen root
> > RPC2 connection to aspen:2432 successful.
> > Returned volume information for root
> >         VolumeId 7f000000
> >         Replicated volume (type 3)
> >
> >         Type0 id 0
> >         Type1 id 0
> >         Type2 id 0
> >         Type3 id 7f000000
> >         Type4 id 0
> >
> >         ServerCount 2
> >         Replica0 id 01000001, Server0 10.1.110.5
> >         Replica1 id 02000001, Server1 10.1.110.6
> >         Replica2 id 00000000, Server2 0.0.0.0
> >         Replica3 id 00000000, Server3 0.0.0.0
> >         Replica4 id 00000000, Server4 0.0.0.0
> >         Replica5 id 00000000, Server5 0.0.0.0
> >         Replica6 id 00000000, Server6 0.0.0.0
> >         Replica7 id 00000000, Server7 0.0.0.0
> >
> >         VSGAddr 0
> >
> > [root_at_aspen ~]# volutil getvolumelist
> > V_BindToServer: binding to host aspen.example.com
> > P/var/vicepa Haspen.example.com Tbe214c Fb98144
> > Wroot.0 I1000001 H1 P/var/vicepa m0 M0 U2 W1000001 C4351577d D4351577d B0
> > A0 GetVolumeList finished successfully
> >
> > [root_at_oak ~]# volutil getvolumelist
> > V_BindToServer: binding to host oak.example.com
> > P/vicepa Hoak.example.com T2cd8ac F2c4684
> > Wroot I2000001 H2 P/vicepa m0 M0 U2 W2000001 C43515a55 D43515a55 B0 A0
> > GetVolumeList finished successfully
Received on 2005-10-16 01:02:55