InnoDB的：无法启动MAMP

Question

当我在MAMP数据库移动到我删除驱动器的过程中，它几乎工作我想，但每当我开始甲基苯丙胺MySQL将不会启动，如果我检查锁定错误45错误日志中我碰到过这样的：

110406 23:00:12 mysqld_safe Starting mysqld daemon with databases from /Volumes/WALL-E/db/mysql 
110406 23:00:12 [Warning] One can only use the --user switch if running as root 

110406 23:00:12 [Note] Plugin 'FEDERATED' is disabled. 
110406 23:00:12 InnoDB: The InnoDB memory heap is disabled 
110406 23:00:12 InnoDB: Mutexes and rw_locks use InnoDB's own implementation 
110406 23:00:12 InnoDB: Compressed tables use zlib 1.2.3 
110406 23:00:12 InnoDB: Initializing buffer pool, size = 128.0M 
110406 23:00:12 InnoDB: Completed initialization of buffer pool 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
110406 23:00:13 InnoDB: Retrying to lock the first data file 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 
InnoDB: Unable to lock /Volumes/WALL-E/db/mysql/ibdata1, error: 45 

我也发现了这个问题但也似乎无法找到一种方法，使对甲基苯丙胺的工作，我在做什么错，它是一个权限问题？

PS - 是的，我的车被称为WALL-E :)

Answer 1

可能与文件系统级的文件锁定的问题。尝试使用--skip-locking启动Mysql。我不知道如何做到这一点与MAMP，因为我从来没有使用它。在首选项中寻找一个地方，您可以为启动提供自定义选项。

或者你可能会打包定制移动媒体的安装，以实现与autofs的锁，但我的autofs福较弱，所以我不能给任何指针那里。