MySQL services stopped and cannot be restarted

  • 7021317
  • 07-Sep-2017
  • 07-Sep-2017


Filr 3.2.1


Filr desktop clients cannot connect.  
MySQL service has stopped; cannot restart the service.
Rebooting does not resolve the problem.


Expand the disk space on the /vastorage disk.  The steps (See "Managing Storage" in the Filr Administration Guide.) are:
  1. Log in to the Filr appliance at https://server_url:9443.
  2. Click Storage.
  3. Use the tools provided by your virtualization platform vendor to expand the virtual disks that contain the partitions your are expanding.
  4. In the provided table, select the partitions to be expanded.
  5. Click Expand partitions.
    Appliance services are stopped, the selected partitions are expanded to the size of their respective disks, and appliance services are restarted.
  6. If there are any Bash console sessions open on the appliance, close them before proceeding to Step 7.
  7. Reboot the appliance so the operating system can detect the disks that have been expanded.


Insufficient disk space for MySQL. The problem can be identified by accessing the Port 9443 Administration Console. Click on the "System Services" button, then on the "download" link for the MySQL service. Examine the log, looking for lines similar to:

170907 10:54:31 [Note] Recovering after a crash using /var/lib/mysql/mysql-bin
170907 10:54:32  InnoDB: Error: Write to file ./filr/SS_WorkAreaFunctionMembers.ibd failed at offset 0 278528.
InnoDB: 16384 bytes should have been written, only -1 were written.
InnoDB: Operating system error number 28.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 28 means 'No space left on device'.

Additional Information

Filr-based personal storage is located on /vashare. See Figure 1.2, 2.4, etc. in Filr 3 - Understanding How Filr Works.
Consider limiting personal storage (My Files) via quotas, etc. See Personal Storage (My Files) Management.