close Warning:

Changes between Version 2 and Version 3 of CodaHOWTO/TroubleShooting


Ignore:
Timestamp:
Feb 8, 2007, 2:47:47 PM (11 years ago)
Author:
jaharkes
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodaHOWTO/TroubleShooting

    v2 v3  
    1111At the end there is a whole section describing how to solve some problems with Windows95, but only the Coda related stuff!
    1212
    13 == Basic Troubleshooting == #BasicTroubleshooting
     13== Basic Troubleshooting == #Basic
    1414
    1515Most 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.
     
    4343 * `/vice/srv/UpdateLog`
    4444
    45 == Client Problems == #ClientProblems
     45== Client Problems == #Client
    4646
    4747 '''Client does not connect to testserver.coda.cs.cmu.edu'''::
     
    108108  * You have tokens
    109109
    110 == Server Problems == #ServerProblems
     110== Server Problems == #Server
    111111
    112112 '''The server crashed and prints messages about !AllocViaWrapAround'''::
     
    240240  When a volume is write-disconnected, it will stay write-disconnected until a user properly authenticates using clog .
    241241
    242 == Advanced Troubleshooting == #AdvancedTroubleshooting
     242== Advanced Troubleshooting == #Advanced
    243243
    244244=== rpc2tcpdump ===
     
    277277# tar -xvzf coda-4.6.5.tgz
    278278}}}
    279 
    280 == Troubleshooting on Windows 95 == #WindowsTrouble
    281 
    282 === Common problems ===
    283 
    284  '''Unable to shutdown Windows95'''::
    285   Check the DOS Windows settings of Venus and Relay. The check box Properties- > Misc- > Termination must be unticked.
    286 
    287  '''I cannot reboot Windows95 and I think it is due to the VXDs loaded for Coda'''::
    288   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
    289 {{{
    290 device=c:\usr\coda\bin\mmap.vxd
    291 device=c:\usr\coda\bin\mcstub.vxd
    292 }}}
    293   Comment them out by using a ; in front of the lines. Try to restart Windows again.
    294 
    295  '''How can I find out why venus.exe crashed'''::
    296   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
    297 {{{
    298 unmount <drive>:
    299 }}}
    300   If it does not work, you want to reboot the machine.
    301 
    302  '''How can I find out more about what has happened'''::
    303   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
    304 {{{
    305 HKLM/System/CurrentControlSet/Services/VxD/Codadev/Debuglevel
    306 }}}
    307   Set the debug level higher than 0 to receive messages in the debug file.
    308 
    309  '''I hook my running machine off the network and the explorer blocks'''::
    310   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.
    311 
    312 === Restrictions ===
    313 
    314  * 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.
    315  * Handling large files (in particular executables) does not work well in a low bandwidth scenario.
    316  * cfs.exe and hoard.exe use absolute pathnames so far.
    317  * Long filenames are not supported under DOS environment yet. You can access files, but you need to use the long filenames.