similar to: Erroneous operation not permitted when deleting mailbox with mdbox

kevent(10,0x0,0,{ 7,EVFILT_READ,0x0,0x0,0x1,0x4207a140 },4,{ 2147483.000000000 }) = 1 (0x1) accept(7,{ AF_UNIX \"\" },0x7fffffffe7fc) = 11 (0xb) getsockname(11,{ AF_UNIX \"/var/run/dovecot/imap-hibe\" },0x7fffffffe7fc) = 0 (0x0) fcntl(11,F_GETFL,) = 6 (0x6) fcntl(11,F_SETFL,O_NONBLOCK|0x2) = 0 (0x0) getpid()

Although the time spent in memcpy/memset probably pales in comparison to time spent in socket I/O, it's still worth worth reducing the number of times we have to utilize a bounce buffer when we already have aligned data. Note that blocksize, cache, and cow all do block fragmentation and bounce-buffer alignment; this brings the logic in cache and cow (which were copied from one another) more

Here's the patch (on top of the preceeding one) which uses a bitmap instead of SEEK_DATA. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org --4VrXvz3cwkc87Wze

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

HI I am running parallel dovecot 1.2 for main accounts and 2.1 for test accounts, and for some reason when i try to login with master user on dovecot 2.1 service errors. However the normal user logins and rest works flawlesly Here is the debug Aug 16 15:15:56 mailstore-node-02 dovecot: auth: Debug: auth client connected (pid=27557) Aug 16 15:15:56 mailstore-node-02 dovecot: auth: Debug: client

On Tue, 2015-11-24 at 17:48 +0300, Yuriy Tabolin wrote: > Thanks for answer. I am very sad to see that. > I had examined samba behavior with tracer and had seen too many poll, > fcntl and stat system calls by samba task[ldapsrv] process > > Elapsed Times for PID 1423, > > SYSCALL TIME (ns) > dup 2653 > flock

Good Afternoon, As per the installation guide, section 30.2.2 I?ve created an efidefault file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault However, this file is never requested by the 64 bit PXE loader (bootx64.efi), as shown by tcpdump: 75 RRQ "/pxelinux/42272635-0011-5053-ACF2-82A100E615F2" octet tsize 0 blksize 512 59 RRQ "/pxelinux/01-00-50-56-A7-BA-BF"

Hi, we've found a weird bug (?) in Dovecot 1.1.11. Since day and age we've been running dovecot for our student mailserver, getting the location of the mailbox from a LDAP directory. We allow login and LDA with both full mail address and an internal username, so the mailbox directory is based on a LDAP attribute user_attrs =

Hello, I am attempting to setup a PXE setup for a network using multiple subnets. The current layout has dhcp on one subnet (10.16.215.8/30), tftp on another (10.16.194.0/23), and the system to be installed on yet another subnet ( 10.16.233.0/24 [there's actually about 30 different subnets the system to be installed could be on]). When I have the system to be installed on the same subnet as

Although the time spent in memcpy/memset probably pales in comparison to time spent in socket I/O, it's still worth worth reducing the number of times we have to utilize a bounce buffer when we already have aligned data. Signed-off-by: Eric Blake <eblake@redhat.com> --- filters/cache/cache.c | 60 ++++++++++++++++++++++++++++--------------- 1 file changed, 39 insertions(+), 21

Hi, since some days (about 10) I get the following error in mail error log many, many times: ... dovecot: imap(user at domain.com pid:32769 session:<dszL7lX1xADD/uGI>): Error: mmap() failed with file /home/dovecotindex/domain.com/user/mailboxes/Trash /dovecot.index.cache: Cannot allocate memory .... It's always the same "dovecot.index.cache" file and only for the same

Hi I'm trying to build a cluster of two servers with dsync replication (based on http://wiki2.dovecot.org/Replication). My test setup works fine for very simple tests, I can log in to both servers, copy a message to one of the servers and it successfully apperars in the other account. But, if I try to copy a large amount of messages at once to one of the accounts, my maillogs get flodded with

Hi! After searching for hours now, I give up and have to ask here. I try to use the expire plugin but it always tries to expire my mails instead of the mails of the user. I read about the "Mail location setting problem (v1.1-v1.2) and configured a "mail" extra field in the userdb, but that doesn't have the effect I want. I have not idea, what I could try out more, so I ask

On 12/2/18 10:33 AM, Richard W.M. Jones wrote: > The cow and cache filters both use a bitmap mapping virtual disk > blocks to status stored in the bitmap. The implementation of the > bitmaps is very similar because one was derived from the other when > the filters were implemented. > > The main difference is the cow filter uses a simple bitmap (one bit > per block), whereas

Gene and co, Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP) It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64. (All my efi x64 content is under efi.x64/pxelinux.cfg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks for these TFTP

Greetings, I'm using the current dovecot release 2.3.10 and I try to rebuild mailboxes with broken attachment paths. When I run this command: doveadm rebuild attachments -u user at example.com ALL I runs fine for 6199 of 6223 messages and fails then at message 6200 with this message: doveadm(user at example.com): Error: Mailbox INBOX: UID=6200:

The cow and cache filters both use a bitmap mapping virtual disk blocks to status stored in the bitmap. The implementation of the bitmaps is very similar because one was derived from the other when the filters were implemented. The main difference is the cow filter uses a simple bitmap (one bit per block), whereas the cache filter uses two bits per block. This commit abstracts the bitmap

Right now, the cache and cow filters always round up requests to blksize boundaries (blksize for cache is dynamically determined at connection start, for cow is fixed as BLKSIZE). Which is fine for the bulk of the underlying file, but can cause problems when reading past EOF for a partial tail of an underlying plugin. We aren't validating that filter calls to next_ops are within bounds; and

The cow and cache filters both use a bitmap mapping virtual disk blocks to status stored in the bitmap. The implementation of the bitmaps is very similar because one was derived from the other when the filters were implemented. The main difference is the cow filter uses a simple bitmap (one bit per block), whereas the cache filter uses two bits per block. This commit abstracts the bitmap

Hey guys, After many trials and tribulations I have now got some fairly stable NFS clients serving dovecot-lda and pop3/imap. Over a 9 hour postal/rabid stress test only saw 5 errors for the 4 servers. Wondering if anyone can shed a bit more light on what they mean exactly. I have tried to find "Resource temporarily unavailable" and "No locks available" in the src to get