Displaying 20 results from an estimated 5000 matches similar to: "Some Information about compression rates to expect using zlib/xz compression"
2020 Aug 28
0
zlib errors after upgrading
zstd support was added in v2.3.11 (not v2.3.12 like I mistakenly tried to say in the earlier mail).
> On 28. Aug 2020, at 16.36, Robert Nowotny <rnowotny at rotek.at> wrote:
>
>
> ok, I did install zstd (zstd command line interface 64-bits v1.4.4, by Yann Collet)
>
> reconfigured & compiled dovecot 2.3.10.1 again with option : with-zstd
>
> changed the
2020 Aug 28
2
zlib errors after upgrading
ok, I did install zstd (zstd command line interface 64-bits v1.4.4, by
Yann Collet)
reconfigured & compiled dovecot 2.3.10.1 again with option : with-zstd
changed the configuration file to :
zlib_save = zstd
and restarted dovecot -
now I have following log file errors :
Aug 28 16:17:39 lxc-imap dovecot:
imap(rnowotny)<237930><H1kft/CtENRUclcc>: Error: zlib_save: Unknown
2020 Aug 28
3
zlib errors after upgrading
unfortunately after re-installing 2.3.11.3, those broken-pipe errors
appear again. (on different, new files)
so for sure there is something broken with zlib.
I will go back to2.3.10.1 now.
attached is the configuration file, though it did not change between
2.3.10.1 and 2.3.11.3
Robert
Am 26.08.2020 um 09:42 schrieb Robert Nowotny:
> I had 4 broken mdbox files for 4 different users.
>
2020 Aug 26
0
zlib errors after upgrading
I had 4 broken mdbox files for 4 different users.
After deleting them, dovecot re-indexed, now everything is ok again.
I can try to update tonight again to 2.3.11.3 and see if some broken
files will appear again tomorrow.
Am 25.08.2020 um 14:51 schrieb Aki Tuomi:
>> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote:
>>
>>
>> I get ZLIB Errors after
2020 Aug 28
0
zlib errors after upgrading
On 28. Aug 2020, at 12.10, Robert Nowotny <rnowotny at rotek.at> wrote:
>
> unfortunately after re-installing 2.3.11.3, those broken-pipe errors appear again. (on different, new files)
> so for sure there is something broken with zlib.
> I will go back to 2.3.10.1 now.
> attached is the configuration file, though it did not change between 2.3.10.1 and 2.3.11.3
Oh, this is
2020 Aug 25
2
zlib errors after upgrading
> On 25/08/2020 14:35 Robert Nowotny <rnowotny at rotek.at> wrote:
>
>
> I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3
>
>
> Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:
2020 Sep 08
2
zlib errors after upgrading to 2.3.11.3
Dear Aki,
I switched to "gz" now, since "zstd" also gave some errors on writing to
files.
I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I
lost 4 days of mail. (a couple of thousand mails).
After restoring the backup (what was made after switching to version
2.3.11.3) I still have some broken mdfiles, but not too many.
Interestingly
2020 Sep 03
0
Fwd: zlib errors after upgrading to 2.3.11.3
Dear Aki,
I switched to "gz" now, since "zstd" also gave some errors on writing to
files.
I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but
I lost 4 days of mail. (a couple of thousand mails).
After restoring the backup (what was made after switching to version
2.3.11.3) I still have some broken mdfiles, but not too many.
2014 May 06
1
WG: on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file
gets corrupted.
the same configuration was working ok on low load with xz compression.
Dovecot Version 2.2.12
Linux Mint 16
EXT4 Filesystem
another dovecot user already reported the same problem on the mailinglist,
using dsync. That user switched to bz2 compression what worked for him.
the answer was :
> are you on
2020 Aug 22
2
zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3
Thunderbird reports some error when try to save/open a bigger attachment.
Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error:
Mailbox Sent: UID=40826:
read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed:
read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken
2014 May 06
0
on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file
gets corrupted.
the same configuration was working ok on low load with xz compression.
Dovecot Version 2.2.12
Linux Mint 16
EXT4 Filesystem
another dovecot user already reported the same problem on the mailinglist,
using dsync. That user switched to bz2 compression what worked for him.
the answer was :
> are you on
2020 Sep 10
0
zlib errors after upgrading to 2.3.11.3
On 10. Sep 2020, at 14.07, Robert Nowotny <rnowotny1966 at gmail.com> wrote:
>
>
> On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966 at gmail.com <mailto:rnowotny1966 at gmail.com>> wrote:
>>
>>>> Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>: Error: Mailbox Sent: UID=2171:
2014 Mar 28
1
Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12
(compiled from source) dsync aborts with a backtrace on some (maybe 15
out of 800) mail accounts:
(same error happens wiht or without -f flag)
dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc:
<snip>
dsync(user at domain.com): Debug: brain M: in state=sync_mails
dsync(user at domain.com): Debug: brain M:
2020 Sep 09
1
zlib errors after upgrading to 2.3.11.3
On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com> wrote:
Dear Aki,
I switched to "gz" now, since "zstd" also gave some errors on writing to
files.
What kind of errors?
Probably this? :
Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion failed:
(!stream->blocking)
can be - unfortunately I do not have the log files anymore...
Sep
2020 Sep 08
1
zlib errors after upgrading to 2.3.11.3
>
> On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com <mailto:rnowotny1966 at gmail.com>> wrote:
>>
>>
>> Dear Aki,
>> I switched to "gz" now, since "zstd" also gave some errors on writing to files.
>
> What kind of errors?
Probably this? :
Panic: file ostream.c: line 287 (o_stream_sendv_int): assertion
2020 Sep 10
2
zlib errors after upgrading to 2.3.11.3
On 9. Sep 2020, at 11.14, Robert Nowotny <rnowotny1966 at gmail.com> wrote:
Sep 3 08:33:25 lxc-imap dovecot: imap(mpaul)<48684><2/9E5mKuAezAqKjk>:
Error: Mailbox Sent: UID=2171:
read(zlib(/home/vmail/virtualmailboxes/mpaul/storage/m.119)) failed:
read(/home/vmail/virtualmailboxes/mpaul/storage/m.119) failed: Broken pipe
(FETCH BODY[])
Also this way you can see if the broken
2020 Sep 08
0
zlib errors after upgrading to 2.3.11.3
On 8. Sep 2020, at 12.35, Robert Nowotny <rnowotny1966 at gmail.com> wrote:
>
>
> Dear Aki,
> I switched to "gz" now, since "zstd" also gave some errors on writing to files.
What kind of errors?
> I dont know if "xz" compression or "zstd" shreddered my MDBOX Files, but I lost 4 days of mail. (a couple of thousand mails).
> After
2002 Jun 21
1
AW: diskspace; was: When will quality increase be unnoti cable?
Yes, you can: whenever you are unable to make a decent backup at least once
a week, your diskspace must be considered to big.
Friedrich
-----Ursprüngliche Nachricht-----
Von: Per Wigren [mailto:wigren@home.se]
Gesendet: Freitag, 21. Juni 2002 07:37
An: vorbis@xiph.org
Betreff: Re: [vorbis] When will quality increase be unnoticable?
<p>Friday 21 June 2002 01.33 skrev Øyvind Stegard:
>
2015 Mar 04
0
ot: maildir has overdrawn his diskspace quota
I have Postfix/Dovecot with virtual domains, same setup unaltered since
server was set up quite a while ago
last month, added a new virtual domain, 'just like before'.
but, today noticed this in the queue/log 'overdrawn his diskspace quota'[1]:
user's Maildir cur has like 48,762,696 bytes (lot less than other users)
tried some searches, found similar probs, but, no
2010 Sep 22
1
xz compression support
Hello,
Just wondering: Dovecot has gzip/bzip2 compression/decompression support.
According to this:
http://stephane.lesimple.fr/wiki/blog/lzop_vs_compress_vs_gzip_vs_bzip2_vs_lzma_vs_lzma2-xz_benchmark_reloaded
gzip and bzip2 aren't really useful together.
While gzip can offer speed and a reasonable amount of compression ratio,
bzip2 is slow, especially on decompression, which Dovecot does