Details
Minor
Description
When running out of disk space during a database import, Maria incorrectly tells me the table is full, as opposed to 'the disk is full'. It seems it's not correctly parsing E_NOSPC and so not returning the correct error string.
cafuego@cachaca:~
; mysql database < data_dump.sql
ERROR 1114 (HY000) at line 676: The table 'cache_menu' is full
cafuego@cachaca:~
; df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/sda6 12G 12G 0 100% /
After making some space available, the import completes fine. I recall reporting this to Sun as well, but I can't find the bug number.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Re: Disk full causes incorrect error message(s)
Confirmed by http://bugs.mysql.com/bug.php?id=44781
Launchpad bug id: 486462
Re: Disk full causes incorrect error message(s)
Ah, found 'im: http://bugs.mysql.com/bug.php?id=44781
The associated syslog entry from the current error was:
Nov 22 10:12:16 cachaca mysqld: 091122 10:12:16 InnoDB: Error: Write to file ./database/cache_menu.ibd f→
Nov 22 10:12:16 cachaca mysqld: InnoDB: 1048576 bytes should have been written, only -1 were written.
Nov 22 10:12:16 cachaca mysqld: InnoDB: Operating system error number 28.
Nov 22 10:12:16 cachaca mysqld: InnoDB: Check that your OS and file system support files of this size.
Nov 22 10:12:16 cachaca mysqld: InnoDB: Check also that the disk is not full or a disk quota exceeded.
Nov 22 10:12:16 cachaca mysqld: InnoDB: Error number 28 means 'No space left on device'.
Nov 22 10:12:16 cachaca mysqld: InnoDB: Some operating system error numbers are described at
Nov 22 10:12:16 cachaca mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/operating-system-error-codes.html
Nov 22 10:12:16 cachaca mysqld: 091122 10:12:16 [ERROR] mysqld: The table 'cache_menu' is full
... so probably the same bug.