Bug #69702 Cannot redirect logs to the root of a windows drive
Submitted: 9 Jul 2013 17:58 Modified: 14 Aug 2013 0:17
Reporter: Todd Schuldt Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Logging Severity:S3 (Non-critical)
Version:5.6.12 OS:Windows (Server 2012 Std)
Assigned to: CPU Architecture:Any

[9 Jul 2013 17:58] Todd Schuldt
Description:
Service is unable to start if the logging files are located at the root of a drive.  Example:  "E:/servername.log", "E:/servername-slow.log" and "E:/servername.err.log" fail to create the log files but "E:/Logs/servername.log", "E:/Logs/servername-slow.log" and "E:/Logs/servername.err.log" do not.

How to repeat:
Install 5.2.12 on Server 2012.  At installation specify path "E:/" at installation for log file location.  Service will fail to start and files will not be created at the drive root.

Suggested fix:
Document that the log files my be at least one directory deep?
[10 Jul 2013 6:14] MySQL Verification Team
it's likely a filesystem permissions problem, can you check that you can normally create files there without requiring elevated privileges?
[10 Jul 2013 11:48] Hartmut Holzgraefe
Could also be a "too many files" problem, drive root directories only have a limited number of slots (512 AFAIR?) while subdirectories are not having any such low hard limit ...
[11 Jul 2013 22:58] MySQL Verification Team
Please check what Shane asked. On Windows 7 I need administrator privileges to create a simple text file in root drive. Thanks.
[12 Jul 2013 22:00] Todd Schuldt
PEBKAC - Sorry for the false alarm.  MySQL Server was installed using the default network service account instead of the custom local user account I specified in my builders doc.
[14 Jul 2013 0:17] MySQL Verification Team
Thank you for the feedback. So issue resolved?. Thanks.
[14 Aug 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".