(Illustration by Gaich Muramatsu)
Hi Anthony, What you see happens when for one reason or another the volume location and/or volume replication database on the server is not updated correctly. You need to go back to the server(s) where you made the volume. On the server hosting the volume check /vice/vol/VolumeList and see if mikevol.0 is in there. Then check the SCM and see if mikevol.0 is in there. Then check the /vice/vol/VRList for mikevol. If you can't find it, or you can find it only in the VolumeList then you should issue a volutil -h "server.holding.volume" purge volname volid If it is there, then it is time to stop and restart the update daemons on all machines. Another thing that can't do any harm is to rebuild the binary databases on the SCM (update moves these to other servers) volutil makevrdb /vice/vol/VRList volutil makevldb /vice/vol/BigVolumeList Then check SrvLog on the SCM for errors. - Peter - > -----Original Message----- > From: AC [mailto:anthchan_at_usa.net] > Sent: Monday, June 02, 1997 9:47 AM > To: coda_at_cs.cmu.edu > Cc: anthchan_at_usa.net > Subject: Seek for your help > > > Sir/Madam, > > I have a question about coda. > > I mount a volume named "mikevol" by using the command "#cfs mkmount > /coda/mikevol mikevol". Then, I find that there is a file which > actually is a symbolic link > (lrwxr-xr-x mikevol->#mikevol) under the directory > "/coda/". I try to use the command "#cd mikevol" to see the content of > this volume, but it replies "no such directories or files". Is it > possible to see the content of this volume? If yes, can you please let > me know how to do it? > > I would be grateful if you can provide me the solution! > > Many Thanks, > Anthony > >Received on 1999-06-02 12:09:21