(Illustration by Gaich Muramatsu)
On Fri, May 11, 2001 at 01:26:31PM +0800, tin wrote: > thank you very much Jan > > where i can setup ROOTVOLUME? (size , and partition ) Ehh, this sounds like a trick question. The name of the root volume should be in /vice/db/ROOTVOLUME on the servers. Where this volume is created doesn't matter. If you've got 2 or more servers, create at least a doubly replicated volume. If the clients have both of the servers listed as root servers they can come up and access the tree even when one of the servers is (temporarily) down. If there is only one server, just create a singly replicated volume, and create a new root volume when servers are added. A lot of this stuff can be found in the "Coda File System User and System Administrators Manual". It's a bit of a read, but it should be worth it. (http://www.coda.cs.cmu.edu/doc/html/manual/book1.html) Most of the time creating a replicated volume is pretty simple, On the SCM: # cat /vice/db/VSGDB E0000100 server1 E0000101 server1 server2 # createvol_rep codaroot E0000101 ... done. Clients query the servers listed as "rootservers" in their configuration file for volume location information. These servers don't necessarily have to export a replica of the rootvolume. Basically when all the rootservers are down a client is unable to find any volumes, however many servers are still up and running. Typically you'd want to avoid depending on programming bugs that take down all servers in a VSG during resolution. So If you have 3 server groups. VSG1 server1,server2,server3 VSG2 server4,server5 VSG3 server6 It is probably best to set rootservers to "server1,server4(,server6)" (pick some server in each VSG). Generally 2 servers should give enough redundancy, # grep rootservers /etc/coda/coda.conf rootservers="server1,server4" JanReceived on 2001-05-11 08:21:30