RAM disk and MySQL service

[philik]

Hello,

Sorry for my english, it's not my native language.

I have a 16Gb RAM disk on a 64Bits 2008R2 server.
I use it as temp disk and for MySQL server socket file.

When I reboot the server, MySQL service do not start, and I have to launch it manually. After manual launch, all work fine.
I suppose that MySQL service start before complete initialization of ramdisk (and so could not find temp disk or could not set socket pipe).

So, I want set MySQL service dependencies but could you tell me wich Windows service I have to wait before starting MySQL ?

Regards
Philippe

[Support]

Hi Philippe,

We are very interested in this issue you mentioned. Our drivers has been started as possible as early and the ramdisk shall be ready before MySQL service starts.

Our drivers are rxvbus.sys and rxvstor.sys.

[philik]

Hello,

Thanks for your answer.

I join a screenshot of my settings.

And a short description of the server :
Bi CPU 2 X X5680
32 Gb RAM
Boot on 3WARE RAID5 HD SAS 15000.
WIndows 2008R2 WebServer edition

Only 1 Ramdisk with Temp folder (and 5 folders creation on init).
Disbling NTFS indexing, set permissions read/write/execute/modify for Everyone.

In fact, this issues occurs only when I set the MySQL socket file location on ramdisk (my.ini => socket = T:/mysql.sock)
And MySQL do not log any error...
If I disable this settings, MySQL start.

I know that RAMDISK driver load as soon as possible, and before MySQL Service. It work fine for all others services (like Zend Server).
As Web Server, there is fewer services as possible, maybe with very fast couple CPU/boot drive, MySQL service start before complete NTFS formatting of RAMDISK ?

I will try some fine tunning in the next days (I could not reboot server during day time) to see if I/O instead SCSI or other change in ramdisk settings can resolve this trouble.
I will try too to set MySQL service to wait a final service is loaded (as IIS for example) and I will post results here.

Regards
Philippe RACHAS

[Support]

Hi Philippe,

Thank you for the detail explanation.

We'll pay more attentions to this issue.