#1159 (in 2.5.7) On fly compression breaks output
I use option:
Save as file
Save on server in
__DB__---[%G-%m-%d--%H-%M]
--------------------------------
So when I set:
Compression "zipped"
all when ok. I get a good ZIP file
test---[2004-03-04--14-43].sql.zip
3,710 KB (3,799,205 bytes)
and all inside ok.
BUT!! When I set:
Compression "gzipped"
I get the file which is only
"154 KB (157,383 bytes)"
or
"154 KB (157,535 bytes)"
Always near these values.
Inside "test---[2004-03-04--14-52].sql.gz"
All begins as normal
===================
# phpMyAdmin SQL Dump
# version 2.5.6
# http://www.phpmyadmin.net
#
# Host: localhost
# Generation Time: Mar 04, 2004 at 02:34 PM
# Server version: 3.23.55
# PHP Version: 4.3.4
#
# Database : `test`
#
# ----------------------------------------------------
----
#
# Table structure for table `OLD_rate`
#
===================
And so on. But then on one of the lines it breakes.
Every time the lines are different.
One more thing.
The files inside
"test---[2004-03-04--14-52].sql.gz"
is "test.sql" and it is about 7 Kb.
As the "gzipped" is 154 KB.
That it.
P.S. In Group: (?) there is no 2.5.6. Only 2.5.6-rc2
Fix it please.
Logged In: YES
user_id=192186
Try disabling CompressOnFly in configuration and say whether
it helps...
Logged In: YES
user_id=771009
Yes.
If I use in "config.inc.php"
$cfg['CompressOnFly'] = FALSE;
then it works fine...
Logged In: YES
user_id=192186
Could you upload here some broken export?
Logged In: YES
user_id=771009
Here.
This is Dump of just installe phpBB2 2.2 (CS version)
The database size is 164.7 KB.
If you look in archive you will see that files inside is only
23327 bytes.
Logged In: YES
user_id=771009
I was mistaken. WinRAR showes that it is 23327 bytes.
But if you unpacked it it will be more than 1mb.
As this site doesn't allow big uploads I put it on my site.
http://makc666.starnet.ru/forum22---\[2004-03-09--21-
17].sql.gz
Logged In: YES
user_id=192186
I probably found the problem, could you please try attached
patch?
Fix for this bug
Logged In: YES
user_id=192186
There was bad detection of write erorr and this error was
not correctly handled then. Fixed in cvs.