(Illustration by Gaich Muramatsu)
On Tue, Aug 22, 2000 at 10:24:04AM -0500, Douglas C. MacKenzie wrote: > Some text/html message about a local-global conflict. The short explanation can be found in the Coda-HOWTO, which happens to also explain everything about the write-disconnected problem that Piotr had. Ofcourse, the howto is very terse, so we have a much more detailed explanation in Coda File System User and System Administrators Manual http://www.coda.cs.cmu.edu/doc/html/manual/book1.html (or as a printable postscript version) http://www.coda.cs.cmu.edu/doc/ps/manual.ps.gz (114439 bytes, 91 pages) The manual has been updated recently, and is still pretty much uptodate (at least for the moment). Jan =Coda-HOWTO============================================================= 4.7 Repairing conflicts Files and directories can get into conflict due to disconnections of clients or servers from the net, as well as through overlapping open/write/close sequences on two clients. A object that is in conflict is representd as a dangling symbolic link and X->@vol.vnode.unique is the file the symlinks points to. How do we get rid of this conflict? 1. type cfs beginrepair X. This changes X from a symlink into a directory. By doing ls X you will see either local global or server1 server2 server3. In the first case we have a local global conflict and in the second case a server server conflict. 2. If the objects in the directory X are files, you have a file conflict, they can also be directories, in which case you can find the content underneath. 3. If you are nervous, this is a good moment to make copy of your files. They can be found under the directory X while the repair session is in progress. 4. cfs endrepair X closes up the repair session. 5. All local global conflicts are repaired with repair. Type repair and follow its cryptic instructions. 6. Server-server conflicts on files are fixed with either filerepair or with removeinc. Server-server conflicts on directories are fixed with repair. =========================================================================Received on 2000-08-22 11:19:03