Changes between Version 2 and Version 3 of CodaHOWTO/TroubleShooting

Timestamp:

Feb 8, 2007, 2:47:47 PM (12 years ago)

Author:

jaharkes

Comment:

--

CodaHOWTO/TroubleShooting

@@ -11 +11 @@
 At the end there is a whole section describing how to solve some problems with Windows95, but only the Coda related stuff!
 
-== Basic Troubleshooting == #BasicTroubleshooting
+== Basic Troubleshooting == #Basic
 
 Most problems can be solved, or at least recognized by using the information logged by the clients and servers. The first step in finding out where the problems stem from is doing a `tail -f` on the log files.
@@ -43 +43 @@
  * `/vice/srv/UpdateLog`
 
-== Client Problems == #ClientProblems
+== Client Problems == #Client
 
  '''Client does not connect to testserver.coda.cs.cmu.edu'''::
@@ -108 +108 @@
   * You have tokens
 
-== Server Problems == #ServerProblems
+== Server Problems == #Server
 
  '''The server crashed and prints messages about !AllocViaWrapAround'''::
@@ -240 +240 @@
   When a volume is write-disconnected, it will stay write-disconnected until a user properly authenticates using clog .
 
-== Advanced Troubleshooting == #AdvancedTroubleshooting
+== Advanced Troubleshooting == #Advanced
 
 === rpc2tcpdump ===
@@ -277 +277 @@
 # tar -xvzf coda-4.6.5.tgz
 }}}
-
-== Troubleshooting on Windows 95 == #WindowsTrouble
-
-=== Common problems ===
-
- '''Unable to shutdown Windows95'''::
-  Check the DOS Windows settings of Venus and Relay. The check box Properties- > Misc- > Termination must be unticked.
-
- '''I cannot reboot Windows95 and I think it is due to the VXDs loaded for Coda'''::
-  Boot your System in DOS mode by pressing F8 on boot time. Cd to the windows directory and type edit system.ini . In the section [enh386] you will find the entries
-{{{
-device=c:\usr\coda\bin\mmap.vxd 
-device=c:\usr\coda\bin\mcstub.vxd
-}}}
-  Comment them out by using a ; in front of the lines. Try to restart Windows again.
-
- '''How can I find out why venus.exe crashed'''::
-  See troubleshooting venus. When this happens it might not be possible to restart Venus, if it is still mounted. In this case try to unmount by typing
-{{{
-unmount <drive>:
-}}}
-  If it does not work, you want to reboot the machine. 
-
- '''How can I find out more about what has happened'''::
-  Look in the file c:\vxd.log . The file system driver codadev.vxd prints information about all requests and answers in this file. the information is only stored if the debug level has been turned on. the debug level is specified in the registry
-{{{
-HKLM/System/CurrentControlSet/Services/VxD/Codadev/Debuglevel
-}}}
-  Set the debug level higher than 0 to receive messages in the debug file. 
-
- '''I hook my running machine off the network and the explorer blocks'''::
-  Venus switches to disconnected mode after a short timeout. After that it should work fine. If it doesn't, check if you have 'network connections' set up in the explorer (e.g. samba drive). 'Network connections' block your system, when no network is available.
-
-=== Restrictions ===
-
- * Most command line tools, that talk to Venus through the ioctl interface of the Coda kernel module seem to work even when they print error messages.
- * Handling large files (in particular executables) does not work well in a low bandwidth scenario.
- * cfs.exe and hoard.exe use absolute pathnames so far.
- * Long filenames are not supported under DOS environment yet. You can access files, but you need to use the long filenames.