I agree with rweaver. In general, you ~really~ don't want your databases sitting on ANY network shared volume:
- Networks are usually orders of magnitude SLOWER than direct hard-disk
- Expensive alternatives (like fibre channel SANs) are an exception ... but you're probably not running fibre channel, are you ?
- "locking" is one thing that will reduce availability and reduce performance
- You can easily saturate your LAN if your application is database intensive
- Basic connectivity:
Networks can fail - that's a fact of life.
MySQL (and most contemporary databases) can recover pretty robustly if the physical network layer hiccups during a client/server connection
It's a whole different story, however, if the physical layer hiccups while server is trying to read a database file that happens to be a network share.
If you're going to use a client/server architecture (like MySQL, SQL Server, Oracle, DB2 or Postgres), then your server's database files should be on local disks.
IMHO .. PSM