bad fsync?
bad fsync?
- Subject: bad fsync?
- From: "A.M." <email@hidden>
- Date: Fri, 18 Feb 2005 10:36:37 -0500
MySQL makes the following claim at:
http://dev.mysql.com/doc/mysql/en/news-4-1-9.html
"InnoDB: Use the fcntl() file flush method on Mac OS X versions 10.3
and up. Apple had disabled fsync() in Mac OS X for internal disk
drives, which caused corruption at power outages."
First of all, is this accurate? A pointer to some docs or a tech note
on this would be helpful.
This change implies that the regular fsync() is somehow intentionally
crippled on 10.3+. What is the reasoning for this and does it truly
have the consequences that MySQL claims (namely, corruption)?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden