search for: max_buffer_size

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

.../* try to keep at least CHUNK_SIZE available */ if (!emxstream->marked && stream->skip > 0) { /* don't try to keep anything cached if we don't have a seek mark. */ i_stream_compress(stream); } if (stream->max_buffer_size == 0 || stream->buffer_size < stream->max_buffer_size) i_stream_grow_buffer(stream, CHUNK_SIZE); if (stream->pos == stream->buffer_size) { if (stream->skip > 0) { /* lose our buffer cache */ i_stream_c...

Having a problem with a mailbox. I've been trying to rebuild - but doveadm force-resync crashes. This is mdbox with sis. doveadm purge -u dmiller at amfes.com doveadm(dmiller at amfes.com): Panic: file istream.c: line 466 (i_stream_grow_buffer): assertion failed: (stream->max_buffer_size > 0) doveadm(dmiller at amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4167a) [0x7fb73465467a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7fb734654762] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb73462c2a0] ->...

Hello, We're having a problem in Dovecot 1.1.8 with a failed assertion on certain mbox format mailboxes. It happens both with deliver when it attempts to delier to the mailbox, and with IMAP connections for the affected box (though I'm not sure what they're doing at the time). Mar 3 12:55:26 <snip> dovecot: Panic: IMAP(<snip>): file istream.c: line 81 (i_stream_read):

Hello Everyone... Some time ago, i send some questions about plugins and concat 2 file handles. So, there is another questions about this. Timo Sirainen send to me this modification, in src/lib-storage/index/maildir/maildir-mail.c struct istream *full_input[3]; full_input[0] = i_stream_create_fd(fd, 0, TRUE); full_input[1] = i_stream_create_fd(fd1, 0, TRUE); full_input[2] = NULL; input =

I've tried to stress test dovecot 1.1.4 with imaptest for days without any assertion failure or crash. Just some "got too little data" messages. So far it's the most stable 1.1.x version. Today a user got this imap segfault with vanilla 1.1.4 (I don't know if it's something you have already fixed in current tree). The user didn't complain of anything, I've just

Today I updated to current dovecot-1.1 hg tree and I got many of these assertion failures: file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (gdb) bt full #0 0x00352402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6

...last_no_newline = <optimized out> last_crlf = <optimized out> no_newline = false crlf_newline = false __FUNCTION__ = "message_parse_header_next" #16 0x00007f328d2fd6c1 in read_header (mstream=0x7df5a0) at istream-header-filter.c:194 max_buffer_size = <optimized out> ret = <optimized out> hdr = 0x0 highwater_offset = <optimized out> ret2 = <optimized out> hdr_ret = <optimized out> #17 i_stream_header_filter_read (stream=0x7df5a0) at istream-header-filter.c:425 mstrea...

...13e6f60 field_idx = <optimized out> count = <optimized out> __FUNCTION__ = "index_mail_parse_header" #10 0x00007f3a7c34779f in read_header (mstream=0x5563c13efef0) at istream-header-filter.c:246 orig_matched = true matched = true max_buffer_size = <optimized out> ret = <optimized out> hdr = 0x5563c13d55a0 highwater_offset = <optimized out> ret2 = <optimized out> hdr_ret = 1 #11 i_stream_header_filter_read (stream=0x5563c13efef0) at istream-header-filter.c:425 mstream =...

After some investigation, it turns out it is non trivial to install dovecot-dbg on debian jessie. Sorry I can't investigate further. Jason Aki Tuomi wrote on 25/3/19 6:12 pm: > Can you install dovecot-dbg and try gdb again? > > Aki > > On 25.3.2019 3.20, Jason Lewis via dovecot wrote: >> Hi, >> >> I've been having an issue with the indexer giving me

...ame); > + sleep(1); > + } > + } > +done: > + pthread_exit(NULL); > +} > + > +/* virtio_console */ > +#define VIRTIO_CONSOLE_FD 0 > +#define MONITOR_FD (VIRTIO_CONSOLE_FD + 1) > +#define MAX_CONSOLE_FD (MONITOR_FD + 1) /* must be the last one + 1 */ > +#define MAX_BUFFER_SIZE PAGE_SIZE > + > +static void * > +virtio_console(void *arg) > +{ > + static __u8 vcons_buf[2][PAGE_SIZE]; > + struct iovec vcons_iov[2] = { > + { .iov_base = vcons_buf[0], .iov_len = sizeof(vcons_buf[0]) }, > + { .iov_base = vcons_buf[1], .iov_len = sizeof(vcons_buf[1]) },...

...ame); > + sleep(1); > + } > + } > +done: > + pthread_exit(NULL); > +} > + > +/* virtio_console */ > +#define VIRTIO_CONSOLE_FD 0 > +#define MONITOR_FD (VIRTIO_CONSOLE_FD + 1) > +#define MAX_CONSOLE_FD (MONITOR_FD + 1) /* must be the last one + 1 */ > +#define MAX_BUFFER_SIZE PAGE_SIZE > + > +static void * > +virtio_console(void *arg) > +{ > + static __u8 vcons_buf[2][PAGE_SIZE]; > + struct iovec vcons_iov[2] = { > + { .iov_base = vcons_buf[0], .iov_len = sizeof(vcons_buf[0]) }, > + { .iov_base = vcons_buf[1], .iov_len = sizeof(vcons_buf[1]) },...

...mpsslog("%s: %s: POLLERR\n", __func__, mic->name); + sleep(1); + } + } +done: + pthread_exit(NULL); +} + +/* virtio_console */ +#define VIRTIO_CONSOLE_FD 0 +#define MONITOR_FD (VIRTIO_CONSOLE_FD + 1) +#define MAX_CONSOLE_FD (MONITOR_FD + 1) /* must be the last one + 1 */ +#define MAX_BUFFER_SIZE PAGE_SIZE + +static void * +virtio_console(void *arg) +{ + static __u8 vcons_buf[2][PAGE_SIZE]; + struct iovec vcons_iov[2] = { + { .iov_base = vcons_buf[0], .iov_len = sizeof(vcons_buf[0]) }, + { .iov_base = vcons_buf[1], .iov_len = sizeof(vcons_buf[1]) }, + }; + struct iovec *iov0 = &vcons_...

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

ChangeLog: ========= v1 => v2: a) License wording cleanup, sysfs ABI documentation, patch 1 refactoring into 3 smaller patches and function renames, as per feedback from Greg Kroah-Hartman. b) Use VRINGH infrastructure for accessing virtio rings from the host in patch 5, as per feedback from Michael S. Tsirkin. v1: Initial post @ https://lkml.org/lkml/2013/7/24/810 Description:

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

An Intel MIC X100 device is a PCIe form factor add-in coprocessor card based on the Intel Many Integrated Core (MIC) architecture that runs a Linux OS. It is a PCIe endpoint in a platform and therefore implements the three required standard address spaces i.e. configuration, memory and I/O. The host OS loads a device driver as is typical for PCIe devices. The card itself runs a bootstrap after