MySQL Bugs: #34823: fsync() occasionally returns ENOLCK and causes InnoDB to restart mysqld

Bug #34823	fsync() occasionally returns ENOLCK and causes InnoDB to restart mysqld
Submitted:	25 Feb 2008 23:52	Modified:	20 Jun 2010 17:15
Reporter:	Alex Rickabaugh	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.1.23-rc	OS:	FreeBSD
Assigned to:	Vasil Dimov	CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

UNVERIFIED DO NOT USE ON PRODUCTION MAY CORRUPT DATA - Test patch to retry the fsync() in a loop on ENOLCK.

Attachment: enolck-retry-loop.patch (text/x-patch), 3.98 KiB.

The solution is to retry operation, here is the patch.

Attachment: bug34823.diff (application/octet-stream, text), 2.10 KiB.