From: Reindl Harald
Date: November 29 2011 1:21pm
Subject: Re: help needed restoring crashed mysql
List-Archive: http://lists.mysql.com/mysql/226384
Message-Id: <4ED4DC42.1080106@thelounge.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig96AA259E923EB747A5A8739A"

--------------enig96AA259E923EB747A5A8739A
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



Am 29.11.2011 14:08, schrieb Luis Pugoy:
> Hello. I have the following problem.
>=20
> I was importing a large database to mysql using mysqldump. Unfortunatel=
y this filled up the whole disk, and
> mysqldump exited with an error that the table it is currently writing t=
o is full. Checking df -h it shows that the
> disk usage is at 100%. I decided to drop the database I was importing, =
but rechecking df -h shows that it is still
> at 100%. I then looked for the cause of this and found a very large fil=
e under /var/lib/mysql. I think it is
> ibdata1.

ibdata1 does NEVER get smaller, this is normal and a hughe problem
in your case, only if you are using "innodb_file_per_table" which
is NOT default would retire the space after drop tables

why is this dumb "innodb_file_per_table=3D0" default since MOST PEOPLE
have only troubles with it because they can not free space with
"optimize table" with no real benefits?


--------------enig96AA259E923EB747A5A8739A
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7U3EIACgkQhmBjz394AnloogCeM2OqOMufC4QY1CGUwaQX05v6
Sz8An3/4ECzyTTJethW8r1Ew3N4cGhCn
=NdHF
-----END PGP SIGNATURE-----

--------------enig96AA259E923EB747A5A8739A--