I thought it may be a nice idea to put the big and zero-ful
SQL databases on e2compr filesystem. Wrong. When
mysqld starts up and reads the "compressed" files the
experiences all kinds of crashing behaviour: kernel
page fail with
register dump, processes die / cant be started, etc.
happens reproducibly on mysqld startup. Several fsck runs
(read: reboots! mysqld got started each time!)
fix the problem, complaining about various files. When
is up again "ibdata1" (main data file) is flagged with "E".
This is kernel 2.4.26 with e2compr on a Celeron 2.4GHz.
the "offending" files are stock mysql distribution (I
had no chance
to cat in the 1 GB-wikipedia dump as I had planned) but
I can provide them. It may also be related to uncommon
method, maybe sparsing write or mmap() or whatever.
MySQL is 4.0.18-1mdk.
e-mail me under email@example.com