I cannot reproduce this bug. The code works as expected, which is to
refuse to start mysql if there are less then 4096 Kbytes of free space
on the partition where /var/lib/mysql is located.

Moreover this fix has been reverted in debian 
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385947).
The fix has been introduced in 5.0.24a-4 (thus in edgy), but reverted in 
5.0.26-1 (thus in feisty), with the following comment:

  The provided patch from bug #385947 was wrong, the variable is called
  BLOCKSIZE not BLOCK_SIZE according to "strings `which df`" (thanks to
  Bruno Muller).

Further investigation shows that df should accept both BLOCKSIZE and
BLOCK_SIZE (http://osdir.com/ml/gnu.core-
utils.bugs/2004-02/msg00132.html).

>From the coreutils info page:

   The default block size is chosen by examining the following
 environment variables in turn; the first one that is set determines the
 block size.

 `DF_BLOCK_SIZE'
     This specifies the default block size for the `df' command.
     Similarly, `DU_BLOCK_SIZE' specifies the default for `du' and
     `LS_BLOCK_SIZE' for `ls'.

 `BLOCK_SIZE'
     This specifies the default block size for all three commands, if
     the above command-specific environment variables are not set.

 `BLOCKSIZE'
     This specifies the default block size for all values that are
     normally printed as blocks, if neither `BLOCK_SIZE' nor the above
     command-specific environment variables are set.  Unlike the other
     environment variables, `BLOCKSIZE' does not affect values that are
     normally printed as byte counts, e.g., the file sizes contained in
     `ls -l' output.

 `POSIXLY_CORRECT'
     If neither `COMMAND_BLOCK_SIZE', nor `BLOCK_SIZE', nor `BLOCKSIZE'
     is set, but this variable is set, the block size defaults to 512.


   If none of the above environment variables are set, the block size
 currently defaults to 1024 bytes in most contexts, but this number may
 change in the future.  For `ls' file sizes, the block size defaults to
 1 byte.

So I'm tempted to mark this bug as invalid.

Mark, are you able to reproduce the behavior ?

It may have been a transient situation where the partition was actually
full, but some space was made later (such as compressing log files in
/var/log).

** Changed in: mysql-dfsg-5.0 (Ubuntu Dapper)
       Status: Triaged => Incomplete

** Tags removed: verification-needed

-- 
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 the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to