Am 03.02.2014 18:08, schrieb ImperialNetwork: > I started to notice this on my error log since i upgraded from 5.5.34 to > 5.5.35: > > 140203 5:26:25 InnoDB: Failed to set O_DIRECT on file > /dev/shm/#sql7e8f6_1a94bc_10.ibd: CREATE: Invalid argument, > continuing anyway > 140203 5:26:25 InnoDB: O_DIRECT is known to result in 'Invalid argument' on > Linux on tmpfs, see MySQL Bug#26662 > > I never seen this error/warning until 5.5.35. Should this be normal?
output of /usr/bin/df -hT would be a good idea if you heave /tmp as tmpfs like more and more linux distributions set "tmpdir" in my.cnf somewhere else, O_DIRECT can not work on tmpfs by definition and that there was before no warning don't mean that it ever worked before there where many warnings in the past 6 months about config options which are deprecated or not work as someone may think the difference is "works not" silent or not silent in most cases
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~maria-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-developers More help : https://help.launchpad.net/ListHelp
