title: Trouble with MySQL - InnoDB: Operating system error number 2 in a file operation
body: <p>I'm developing locally and using Mamp Pro.
  Basically MySQL is having trouble starting and here's the error message from the error log:</p>
  
  <p>Any idea how to resolve this?</p>
  
  <pre><code>2017-03-02 00:39:08 9518 [Note] Plugin 'FEDERATED' is disabled.
  2017-03-02 00:39:08 9518 [Note] InnoDB: Using atomics to ref count buffer pool pages
  2017-03-02 00:39:08 9518 [Note] InnoDB: The InnoDB memory heap is disabled
  2017-03-02 00:39:08 9518 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
  2017-03-02 00:39:08 9518 [Note] InnoDB: Memory barrier is not used
  2017-03-02 00:39:08 9518 [Note] InnoDB: Compressed tables use zlib 1.2.8
  2017-03-02 00:39:08 9518 [Note] InnoDB: Using CPU crc32 instructions
  2017-03-02 00:39:08 9518 [Note] InnoDB: Initializing buffer pool, size = 128.0M
  2017-03-02 00:39:08 9518 [Note] InnoDB: Completed initialization of buffer pool
  2017-03-02 00:39:08 9518 [Note] InnoDB: Highest supported file format is Barracuda.
  2017-03-02 00:39:08 9518 [Note] InnoDB: Log scan progressed past the checkpoint lsn 663573438
  2017-03-02 00:39:08 9518 [Note] InnoDB: Database was not shutdown normally!
  2017-03-02 00:39:08 9518 [Note] InnoDB: Starting crash recovery.
  2017-03-02 00:39:08 9518 [Note] InnoDB: Reading tablespace information from the .ibd files...
  2017-03-02 00:39:08 9518 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta uses space ID: 367 at filepath: ./affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta.ibd. Cannot open tablespace freshwp/freshwp_wfblocksadv which uses space ID: 367 at filepath: ./freshwp/freshwp_wfblocksadv.ibd
  2017-03-02 00:39:08 7fff7b652000  InnoDB: Operating system error number 2 in a file operation.
  InnoDB: The error means the system cannot find the path specified.
  InnoDB: If you are installing InnoDB, remember that you must create
  InnoDB: directories yourself, InnoDB does not create them.
  InnoDB: Error: could not open single-table tablespace file ./freshwp/freshwp_wfblocksadv.ibd
  InnoDB: We do not continue the crash recovery, because the table may become
  InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
  InnoDB: To fix the problem and start mysqld:
  InnoDB: 1) If there is a permission problem in the file and mysqld cannot
  InnoDB: open the file, you should modify the permissions.
  InnoDB: 2) If the table is not needed, or you can restore it from a backup,
  InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
  InnoDB: crash recovery and ignore that table.
  InnoDB: 3) If the file system or the disk is broken, and you cannot remove
  InnoDB: the .ibd file, you can set innodb_force_recovery &gt; 0 in my.cnf
  InnoDB: and force InnoDB to continue crash recovery here.
  170302 00:39:08 mysqld_safe mysqld from pid file /Applications/MAMP/tmp/mysql/mysql.pid ended
  </code></pre>
  
  <p><strong>From the above code the error seems to be:</strong></p>
  
  <p>2017-03-02 00:39:08 9518 [ERROR] InnoDB: Attempted to open a previously opened tablespace. </p>
  
  <p>Previous tablespace affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta 
  uses space ID: 367 
  at filepath: ./affiliate_blog_1_old/wpab1_7_woocommerce_order_itemmeta.ibd. </p>
  
  <p>Cannot open tablespace freshwp/freshwp_wfblocksadv which uses space ID: 367 
  at filepath: ./freshwp/freshwp_wfblocksadv.ibd</p>