1 This file is a rough list of known issues with the 1.3.72 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) File termination differences between Win9x and nt/w2k/xp (Jim Peterson)
34 (8) How to silence "Explorer" when the mapped drive is not available?
36 (9) Convert to IFS!!!!!!
38 (10) Kerberos 5 integration:
39 (10f) allow arbitrary cell to realm mappings
40 (10g) modify UI to allow user to choose whether to authenticate
42 (10h) modify UI to allow user to select an existing principal to
43 be used to request AFS tokens
44 (10i) modify UI to display Kerberos 5 ticket info (principal,
45 ticket lifetimes, etc)
47 (11) Default cell is system global just like everything else. Different
48 users logging in via Integrated Logon or using afscreds.exe cannot
49 be automatically prompted for different cells
51 (12) AFS Integrated Logon:
52 (12b) If using Kerberos, need to figure out a means of passing credentials
53 into the user space until such time as I finish the new credential
55 (12c) If network is not available must store the username and password
56 somewhere until such time as the network starts.
58 (13) Loopback adapter is not always installed with bindings to "File and
59 Printer Sharing for Microsoft Networks" or "Client for Microsoft
60 Networks". If these are not bound then SMB names will successfully
61 be published to a list of zero which causes the AFS not to function.
62 We need a way to test whether the Loopback adapter is properly bound
63 so we know if it is safe to use. Actually, it is worse. Even with
64 the bindings on Win2000 the loopback adapter frequently fails to publish
65 SMB names. Of course, the error messages report nothing.
67 (14) If a drive mapping is "in use", then afscreds cannot be used to Modify
68 or Delete the Mapping. If a map to "H:" to \afs\cell\foo" with
69 description "home" is modified to point to \afs\cell\bar, then the
70 description must be unique. "home" cannot be reused. We need a way
71 to remove "home" from the submount list.
73 [Actually, an end user should not be able to modify the submount list]
75 (15) Drive mappings are lost on WinXP after return from Standby. (This could
76 be because the AFS Client Service fails OR because the RX protocol is
77 temporarily unable to access the Cell due to network restore timing
80 (16) No support for Unicode CIFS/SMB data structures. OEM Code Pages prevent
81 the use of interoperable file names; force the use of paths no longer
82 than 256 characters; force share names to be no longer than 13
83 characters; restrict authentication to ASCII only names and passwords;
86 (17) No auto-restart on service failure
88 (18) Better EventLog handling
90 (19) Named Pipes Support [requires modifications to AFS servers to support]
92 (20) Memory Mapped File support
94 (21) Large file support [both SMB/CIFS and AFS]
96 (22) Implement persistent disk based cache which survives restarts
98 (23) NSIS Installer issues
99 (a) integration with KFW install script
100 (b) Optional removal of AFS Server volumes
102 (24) The User Interface needs to be re-designed to separate the per-user
103 and per-machine settings. All of the new registry items need to
106 (25) Thread initialization versus Global Drive Mapping. There is no
107 mechanism in the afsd_init.c to ensure that all of the threads
108 complete initializing in the correct sequence. In the case of
109 Global Drive Maps this is a problem because the Global Drive Maps
110 can be executed prior to the completion of the SMB registration
111 and service thread initialization.
113 (26) CIFS Remote Administration Protocol implementation is incomplete.
114 Notifications are not made to requestors when the view of a file
115 or folder changes due to token acquisition; token expiration; or
118 (27) The Cache Manager Flush routines do not return or check error
121 (28) Remove submount creation as a side effect of AFS drive mapping.
123 The AFS Submount is effectively a server side alias for a path
124 located in the AFS space. This alias is exported by the AFS
125 SMB/CIFS Server to the Windows SMB/CIFS client as a Share name.
126 This makes the AFS Submount a system global setting which should
127 only be modified by a member of the "AFS Client Admin" group.
129 afs_creds.exe and afs_config.exe should be modified to no longer
130 use submount names when creating drive maps. Drive maps should
131 simply use the full AFS path name. Submounts should not be
132 created as a side effect of a drive mapping.
134 The creation of submounts should only be possible via afsshare.exe
135 or by the new AFS Client Service Administration tool when executed
136 by an authorized user.
138 (29) Add support for multi-homed servers
141 -------------------------------------------------------------------------
142 List of unfunded projects:
144 1. No longer use AFS Client Service "cell" as the default cell for individual users
145 2. Re-write afsd_service.exe to perform synchronized thread startup and shutdown.
146 Currently there is no synchronization of thread creation which results in timing
147 conflicts; and there is no attempt to cleanly shutdown the service which causes
148 problems when restarting and prevents the implementation of a persistent cache
149 3. Implement a persistent cache (requires item 2)
150 4. Prevent panic situation when the root.afs volume is not reachable and
151 the AFS Client Server is not using Freelance mode
152 5. Prevent panic situation when the IP address to which the SMB server is bound is removed
153 from the local machine's network configuration
154 6. Add support for Named Pipes within the afs filesystem
155 (This is not currently a supported feature of AFS; it will require
156 changes to the servers as well as the clients.)
157 7. Re-write afscreds.exe to support:
158 1. choosing between Kerberos 5 and Kerberos 4 on a per principal basis
159 2. providing users with the ability to map multiple cells to a single principal
160 3. providing change password functionality on a per principal basis
161 4. no longer include drive mapping
162 5. configuration of afscreds startup options in shortcut
163 8. Re-write afs_config.exe to be only "per user" functionality which does not require admin
165 1. default cell and principal for the user
166 2. drive mappings but no submounts
167 3. visibility of afs creds and setting of afs creds startup options
168 9. Create new afs_admin.exe tool to be installed in the administrator folder (or use MMS)
170 1. afs client service cell name
171 2. integrated logon configuration
172 3. Gateway configuration
173 4. start/stop service
174 5. global drive mapping
175 6. submount management
176 7. file/volume server preferences
178 9. cache configuration
180 11. network configuration
182 13. need to add support for all of the new registry values since 1.2.8
183 10. Identify why 16-bit DOS applications executed out of AFS fail
184 11. Add support for configurable Icon file representing AFS folders within the Explorer Shell
185 12. Documentation Documentation Documentation
186 13. Large File support (> 2GB) in SMB/CIFS client
187 14. Integrate KFW installation into the NSIS and MSI installers
188 15. Add support for record locking to AFS (requires changes to the servers)
189 16. Unicode enable the SMB/CIFS server. OEM Code Pages:
190 1. prevent the use of interoperable file names
191 2. force the use of paths no longer than 256 characters
192 3. force share names to be no longer than 13 characters
193 4. restrict authentication to ASCII only names and passwords
194 17. Complete implementation of CIFS Remote Administration Protocol
195 19. Add support for SMB/CIFS Digital Signatures
196 19. Development of afsmap.exe tool to provide AFS aware NET USE functionality
197 afsmap.exe <drive> <afs-path> [/PERSISTENT]
198 afsmap.exe <drive> <unc-path> [/PERSISTENT]
199 afsmap.exe <drive> /DELETE
200 20. Missing SMB/CIFS functions:
208 21. StoreBehind mode is not implemented. Or more correctly, all data is
209 written directly to the server and is not cached. Writes invalidate
210 the local cache entries which are then read back from the server.
211 22. The Power Management Flush Cache code does not work on Terminal
212 Server nor does it always successfully flush all of the dirty buffers
213 to the AFS servers before suspend/hibernate operations occur.
214 23. Develop an optional Installable File System replacement for the SMB/CIFS
216 24. Add support for storing Extended Attributes on files
217 25. Add support for storing Windows ACLs on files
218 26. Remove submount creation as a side effect of drive creation
219 27. Finish conversion from string.h to strsafe.h for VS.NET 2005
220 28. Add support for multi-homed servers