1 This file is a rough list of known issues with the 1.3.65 release of OpenAFS
2 on Windows. This list is not complete. There are probably other issues
3 which can be found in the RT database or on the mailing list.
6 (1) File/Directory access is not integrated with windows security
8 (3) SMB LANA list is static.
10 (3a) IP address changes cause the service to terminate due to an assertion
11 in smb_Listener() thread.
13 (3b) New IP addresses do not get bound
15 (3c) Loopback adapter hack:
16 (i) prevents use of AFS Gateway
17 (ii) requires installation of loopback adapter
18 (iii) the list of hack adapters is incomplete (VMWare, MS TV/Video, ...)
19 (iv) incompatible with Windows 2000 and earlier
21 (4) Performance of the AFS Client Service code simply sucks. The average
22 read, write, and delete times for AFS are more than ten times slower than
23 the equivalent Windows File Share operations. The Window File Share operations
24 are not all that fast. It has been claimed that the Windows AFS functions are
25 one hundred times slower than the equivalent operations on Linux. I would not
26 be at all surprised. The best we can do without rewriting AFS as a IFS would
27 be to match the Windows File Share performance. I believe the threading model
28 is imposing significant delays in the movement of data from between the SMB
29 and RX protocol operations. There was also an issue with large numbers of
30 page faults which have since been fixed.
32 (7) There appear to be directory locking problems associated with renaming
35 (8) File termination differences between Win9x and nt/w2k/xp (Jim Peterson)
37 (9) How to silence "Explorer" when the mapped drive is not available?
39 (10) Convert to IFS!!!!!!
41 (11) Kerberos 5 integration:
42 (11f) allow arbitrary cell to realm mappings
43 (11g) modify UI to allow user to choose whether to authenticate
45 (11h) modify UI to allow user to select an existing principal to
46 be used to request AFS tokens
47 (11i) modify UI to display Kerberos 5 ticket info (principal,
48 ticket lifetimes, etc)
50 (12) Default cell is system global just like everything else. Different
51 users logging in via Integrated Logon or using afscreds.exe cannot
52 be automatically prompted for different cells
54 (13) AFS Integrated Logon:
55 (13b) If using Kerberos, need to figure out a means of passing credentials
56 into the user space until such time as I finish the new credential
58 (13c) If network is not available must store the username and password
59 somewhere until such time as the network starts.
61 (14) Loopback adapter is not always installed with bindings to "File and
62 Printer Sharing for Microsoft Networks" or "Client for Microsoft
63 Networks". If these are not bound then SMB names will successfully
64 be published to a list of zero which causes the AFS not to function.
65 We need a way to test whether the Loopback adapter is properly bound
66 so we know if it is safe to use. Actually, it is worse. Even with
67 the bindings on Win2000 the loopback adapter frequently fails to publish
68 SMB names. Of course, the error messages report nothing.
70 (15) If a drive mapping is "in use", then afscreds cannot be used to Modify
71 or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with
72 description "home" is modified to point to \afs\cell\bar, then the
73 description must be unique. "home" cannot be reused. We need a way
74 to remove "home" from the submount list.
76 (16) WinAFS configuration values are still stored in old style INI files
77 instead of using the Registry. This is especially important for
78 per-user values such as drive mappings
80 (17) Drive mappings are lost on WinXP after return from Standby. (This could
81 be because the AFS Client Service fails OR because the RX protocol is
82 temporarily unable to access the Cell due to network restore timing
85 (18) No support for Unicode filenames. Translations make file unreadable
87 (19) No auto-restart on service failure
89 (20) Better EventLog handling
91 (21) Named Pipes Support
93 (22) Memory Mapped File support
95 (23) Large file support
97 (26) Implement persistent disk based cache which survives restarts
99 (27) NSIS Installer issues
100 (a) integration with KFW install script
101 (b) Optional removal of AFS Server volumes
103 (28) The User Interface needs to be re-designed to separate the per-user
104 and per-machine settings. All of the new registry items need to
107 (30) There appears to be a thread safety issue in the Rx library when
108 running on Intel processors which support hyper-threading
110 (32) Thread initialization versus Global Drive Mapping. There is no
111 mechanism in the afsd_init.c to ensure that all of the threads
112 complete initializing in the correct sequence. In the case of
113 Global Drive Maps this is a problem because the Global Drive Maps
114 can be executed prior to the completion of the SMB registration
115 and service thread initialization.
117 (35) Should we allow the AFSCACHE file to be stored in the Virtual Paging
118 file as long as we do not support persistent caches?
121 -------------------------------------------------------------------------
124 1. No longer use AFS Client Service "cell" as the default cell for individual users
125 2. Re-write afsd_service.exe to perform synchronized thread startup and shutdown.
126 Currently there is no synchronization of thread creation which results in timing
127 conflicts; and there is no attempt to cleanly shutdown the service which causes
128 problems when restarting and prevents the implementation of a persistent cache
129 3. Implement a persistent cache
130 4. Prevent panic situation when the root.afs volume is not reachable
131 5. Prevent panic situation when the IP address to which the SMB server is bound is removed
132 from the local machine's network configuration
133 6. Identify and fix the problems with running the RX library on Hyperthreaded systems
134 7. Add support for Named Pipes within the afs filesystem
135 (This is not currently a supported feature of AFS; it will require
136 changes to the servers as well as the clients.)
137 8. Re-write afscreds.exe to support:
138 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
139 2. providing users with the ability to map multiple cells to a single principal
140 3. providing change password functionality on a per principal basis
141 4. no longer include drive mapping
142 5. configuration of afscreds startup options in shortcut
143 9. Re-write afs_config.exe to be only "per user" functionality which does not require admin
145 1. default cell and principal for the user
147 3. visibility of afs creds and setting of afs creds startup options
148 10. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
150 1. afs client service cell name
151 2. integrated logon configuration
152 3. Gateway configuration
153 4. start/stop service
154 5. global drive mapping
155 6. submount management
156 7. file/volume server preferences
158 9. cache configuration
160 11. network configuration
162 13. need to add support for all of the new registry values since 1.2.8
163 11. Identify why 16-bit DOS applications executed out of AFS fail
164 12. Create new Windows Security Group to which users can be added for them to become AFS
165 Client Administrators
166 13. Add support for configurable Icon file representing AFS folders within the Explorer Shell
167 14. Documentation Documentation Documentation
168 15. Large File support (> 2GB)
169 16. Integrate KFW installation into the NSIS installer
170 17. Add support for record locking to AFS (requires changes to the servers)