I tend to agree with Mathias and tempted to mark this report as invalid. df -P (or --portability) is not affected by BLOCK_SIZE or BLOCKSIZE settings.
Just a simple test shows that this setting is ignored with -P (I've just left the header line for clarity but you can see the effect of BLOCKSIZE in the 2nd colum of the header): $:/tmp$ df . Filesystem 1K-blocks Used Available Use% Mounted on $:/tmp$ BLOCKSIZE=1M df . Filesystem 1M-blocks Used Available Use% Mounted on $:/tmp$ df -P . Filesystem 1024-blocks Used Available Capacity Mounted on $:/tmp$ BLOCKSIZE=1M df -P . Filesystem 1024-blocks Used Available Capacity Mounted on Hence, the line in the init script will always return the same thing whatever BLOCKSIZE or BLOCK_SIZE value is. The error encountered by the original submitter and Guillaume are probably due to a temporary lack of space. -- mysql server fails to start, claims /var/lib/mysql full https://bugs.launchpad.net/bugs/118523 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
