search for: zstream

Greetings, I noticed a while back someone posted a patch/plugin that allowed Dovecot to use compressed mbox files. I'm now wondering how far that would put us from having compressed maildir? I have a server with more CPU than disk space, and while I can buy more HDD space, my backup solution doesn't make that practical. It seems to me that when looking for a message file, if it

...mail encrypt size = 49568 Attachements: mail-arrived, is when the email arrives, and it's ok the read. mail-receive, is when the email is received, and have the error. maillog is the /var/log/mail The bigger difference from zlib is the i_stream_zlib_read part.... do { ret = read(zstream->fd ,crypttext, size); fprintf(zstream->debug,"DENTRO DA READ RET = %d -- ERRNO = %d -- STR = |%s|\n", ret, errno, strerror(errno)); if(ret > 0){ EVP_DecryptUpdate(&ctx, plaintext, &plain_len, crypttext, ret); memcpy(stream->w_bu...

Hello, I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs are producing these errors every so often, but AFAICT the messages themselves aren't getting corrupted. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal: master: service(imap): child 80128 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream....

...gt;> I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs >> are producing these errors every so often, but AFAICT the messages >> themselves aren't getting corrupted. >> Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion >> failed: (zstream->ostream.finished || >> zstream->ostream.ostream.stream_errno != 0) >> Fatal: master: service(imap): child 80128 killed with signal 6 (core >> not dumped - set service imap { drop_priv_before_exec=yes }) >> Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): ass...

I see this in my logs after 2.3.3: using zlib plugin, ofc. Oct 02 10:01:39 imap(user at example.com)<50643></2k4Sjp3vMqC496W>: Panic: file ostream-zlib.c: line 37 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0 || zstream->ostream.error_handling_disabled) Oct 02 10:01:39 imap(user at example.com)<50643></2k4Sjp3vMqC496W>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xce56a) [0x7f442487556a] -> /usr/lib...

Hi Timo, As a follow-up to my earlier email, I've managed to get a few backtraces now. #305439 o_stream_close (stream=0x1680c10) at ostream.c:85 #305440 0x00007ff222f70f3c in o_stream_zlib_send_outbuf (zstream=0x1680b80) at ostream-zlib.c:97 #305441 0x00007ff222f70fef in o_stream_zlib_send_flush (zstream=0x1680b80) at ostream-zlib.c:182 #305442 0x00007ff222f711cb in o_stream_zlib_flush (stream=<optimized out>) at ostream-zlib.c:222 #305443 0x00007ff2243f142d in o_stream_flush (stream=0x1680c10) at...

...Hello, > > I use the zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs > are producing these errors every so often, but AFAICT the messages > themselves aren't getting corrupted. > > Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion > failed: (zstream->ostream.finished || > zstream->ostream.ostream.stream_errno != 0) > Fatal: master: service(imap): child 80128 killed with signal 6 (core > not dumped - set service imap { drop_priv_before_exec=yes }) > Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion > fail...

...e zlib and imap_zlib plugins on FreeBSD. As of 2.3.0, my logs >>> are producing these errors every so often, but AFAICT the messages >>> themselves aren't getting corrupted. >>> Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion >>> failed: (zstream->ostream.finished || >>> zstream->ostream.ostream.stream_errno != 0) >>> Fatal: master: service(imap): child 80128 killed with signal 6 (core >>> not dumped - set service imap { drop_priv_before_exec=yes }) >>> Panic: file ostream-zlib.c: line 36 (o_stream_...

...__FUNCTION__ = "o_stream_sendv" #10 0x00007f11766e615a in o_stream_send (stream=<optimized out>, data=<optimized out>, size=size at entry=12113) at ostream.c:217 iov = {iov_base = 0x7f11789fe549, iov_len = 12113} #11 0x00007f1175692849 in o_stream_zlib_send_outbuf (zstream=0x7f11789f9340) at ostream-zlib.c:94 ret = <optimized out> size = 12113 #12 0x00007f1175692982 in o_stream_zlib_send_flush (zstream=zstream at entry=0x7f11789f9340, final=final at entry=true) at ostream-zlib.c:189 zs = 0x7f11789f9420 len = <optimized out>...

...boxes were not compressed). It seems that when the zlib plugin is enabled, but zlib_save isn't set, the zlib plugin aborts on a regular basis---on a single-user system, I was seeing it about 150 times a day. Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || zstream->ostream.ostream.stream_errno != 0) Fatal: master: service(imap): child 80128 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Removing the (unused) zlib plugin made the errors disappear, at least. # Adam -- Adam Wein...

Hi! After upgrade I'm noticing many coredummps, below is backtrace: $ echo "bt"|gdb .... #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 222 if (o_stream_zlib_send_flush(zstream) < 0) (gdb) #0 o_stream_zlib_flush (stream=0xc8be5b27640) at ostream-zlib.c:222 #1 0x00007a695e8f09cd in o_stream_flush (stream=stream at entry=0xc8be5b276d0) at ostream.c:147 #2 0x00007a695e83c06f in o_stream_zlib_close (stream=0xc8be5b27640, close_parent=true) at ostream-zlib.c:35 #3 0x000...

Hi, after updating Dovecot to version 2.3 I get a lot of core-dumps like: > Jan 18 10:08:20 mail dovecot: imap(bob at tutech.de)<18200><CIPhNwljJcdYS/hg>: Panic: file ostream-zlib.c: line 36 (o_stream_zlib_close): assertion failed: (zstream->ostream.finished || > zstream->ostream.ostream.stream_errno != 0) > Jan 18 10:08:20 mail dovecot: imap(bob at tutech.de)<18200><CIPhNwljJcdYS/hg>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc71da) [0x7f9b510c81da] -> /usr/lib64/dovecot > /libdovecot....

Hi, I just learned that there exists a "z-stream" channel upstream that apparently carries some important bugfixes. Does anyone know what the policies are for this channel and how this relates to centos releases? Regards, Dennis

We've come across a problem with 6.4 kernels that we didn't have with 6.2 kernels - which involves writing to a symlink that is on a read-only file system - but the symlink lands on a read-write file system The following shows the issue: mkdir -p /mnt/tmp mount -t tmpfs -o size=1% none /mnt/tmp rm -f /tmp/file ln -s /tmp/file /mnt/tmp/file mount -o remount,ro /mnt/tmp echo

...extern int kvm_allowed; extern int kvm_irqchip; Index: kvm-userspace/qemu/vl.c =================================================================== --- kvm-userspace.orig/qemu/vl.c +++ kvm-userspace/qemu/vl.c @@ -7216,6 +7216,30 @@ static void ram_decompress_close(RamDeco inflateEnd(&s->zstream); } +#ifdef USE_KVM +extern int64_t target_ramsize; /* qemu/hw/virtio-balloon.c */ +static void balloon_save(QEMUFile *f, void *opaque) +{ + qemu_put_be64(f, target_ramsize); +} + +static int balloon_load(QEMUFile *f, void *opaque, int version_id) +{ + int64_t target; + + if (version_id...

...extern int kvm_allowed; extern int kvm_irqchip; Index: kvm-userspace/qemu/vl.c =================================================================== --- kvm-userspace.orig/qemu/vl.c +++ kvm-userspace/qemu/vl.c @@ -7216,6 +7216,30 @@ static void ram_decompress_close(RamDeco inflateEnd(&s->zstream); } +#ifdef USE_KVM +extern int64_t target_ramsize; /* qemu/hw/virtio-balloon.c */ +static void balloon_save(QEMUFile *f, void *opaque) +{ + qemu_put_be64(f, target_ramsize); +} + +static int balloon_load(QEMUFile *f, void *opaque, int version_id) +{ + int64_t target; + + if (version_id...