Bug #15325 initializing raw partition with INNODB extraordinarily clumsy
Submitted: 29 Nov 2005 19:05 Modified: 13 May 2010 16:04
Reporter: Eric Goff Email Updates:
Status: Open Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S4 (Feature request)
Version:5.0.16 OS:Linux (Linux)
Assigned to: Assigned Account CPU Architecture:Any
Triage: D5 (Feature request)

[29 Nov 2005 19:05] Eric Goff
Description:
To initialize a raw partition, I have to
      edit my.cnf to specify newraw
      start mysqld
      wait for it to finish
      edit my.cnf again to specify simply raw
      restart mysqld

While this might be easy for an administrator to do,
I would like you to think about what this means to
an automated process. 

An automated process has to constantly read
      the server.err to find out when the process of initialization
      has completed.

How to repeat:
Try to write a robust way to initialize a raw partition.
You will see how clumsy it is.

Suggested fix:
Write a program to initialize raw partition.
Or........
Provide a way for mysqld_safe to exit when it has finished
initializing.
[30 Nov 2005 11:25] Heikki Tuuri
Eric,

raw partitions are useful only if fsync() is slow in your OS. Is that the case?

Regards,

Heikki
[30 Nov 2005 15:11] Eric Goff
I would not say that fsync is especially slow, but I will be doing
a lot of them.  This database will be inserting roughly 10,000 inserts/sec.