this is most likely a wrong assumption, you are probably just seeing this informational message which seems like an error:
https://bugs.launchpad.net/percona-server/+bug/747032
what I think is actually happening is your security system (SELinux?) blocking access to /raid/mysql for MySQL, you should either properly configure the security system or disable it altogether.
Aurimas
> --
> You received this message because you are subscribed to the Google Groups "Percona Discussion" group.
> To post to this group, send email to percona-d...@googlegroups.com.
> To unsubscribe from this group, send email to percona-discuss...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/percona-discussion?hl=en.
>
--
Aurimas Mikalauskas, Principal Consultant, Percona Inc.
Lithuania, Eastern Europe (GMT +2)
+1 888 401 3401 | Aurimas x503 | 24x7 Help x911
Join us at Percona Live London!
http://www.percona.com/live/london-2011/
Aurimas
I fear you may have been right. My knowledge of device-mapper is
pretty anemic, but it appears that dm-2 points to the logical volume
mounted to /raid, the partition containing /raid/mysql (my datadir).
So perhaps MySQL is just trying to write to its own data directory,
which should theoretically be allowed, but for whatever reason, is
not.
Any other ideas? I fear I may be about to jump down a SELinux rabbit-hole.
Norman
My experience with SELinux is that it is best to disable it. SELinux
can not only be extremely difficult to administer and configure, but
anecdotally, it causes a pretty significant performance impact on
MySQL. And it's not clear to me that the attack vectors it
theoretically helps prevent are worth the trade-off. I fear that a
system administrator who fights with SELinux to get MySQL working may
actually leave the system in an unknown or unclean state, and end up
making the system less secure, through failed attempts to fix it.
- Baron