similar to: Any feature allow to add lock on a file between different apps?

Hello - I know I am not the only one that will be trying, or has tried this before. Here are my questions! NFS Clients, multiple servers running dovecot - linux with 2.6 kernel with relevant patches (utime, etc) Backend - netapp filer End users - various clients all running IMAP It looks like 1.0.beta8 is definately the way to go. I have a few questions with regards to setup. Is it now

/etc/postfix/main.cf.default: mailbox_delivery_lock = flock, dotlock Is flock equivalent to dovecot's fnctl locking? For mbox what type of locking settings should I be using? (No NFS, only local filesystem.) Warren Togami warren at togami.com

Hi everyone, I have noticed recently that Dovecot creates lock directories under users' Maildirs which look like IMAP folders. This is bad since users will see IMAP folders that are not supposed to be there. In my logs I see dovecot: imap(...): Error: file_create_locked(/.../Maildir/.vsize.lock) failed: Is a directory The directory in question # ls /.../Maildir/.vsize.lock/ cur/

I'm just dumping all I got in here, after initial feedback we can see how to organize todo's around it. tl;dr: * Does not upgrade cleanly from 4.8 packages, so we have to prevent this from entering testing until we fix that. * Live migration is broken, explodes with memory allocation errors. ---- >8 ---- 1. Build packages * I have built salsa/master using pbuilder targeting sid.

Hi, I did some experiments with dovecot on a glusterfs on the active nodes without a director. So I had concurrent access to the files. With the help of the available documentation about NFS and fcntl locks I managed to find out the following: With the plain mbox format dovecot seems to apply and to honor the fcntl locks. But since this format is not used any more in real setups, it is

Firstly, it isn't necessary to hold lock of vblk->vq_lock when notifying hypervisor about queued I/O. Secondly, virtqueue_notify() will cause world switch and it may take long time on some hypervisors(such as, qemu-arm), so it isn't good to hold the lock and block other vCPUs. On arm64 quad core VM(qemu-kvm), the patch can increase I/O performance a lot with VIRTIO_RING_F_EVENT_IDX

Firstly, it isn't necessary to hold lock of vblk->vq_lock when notifying hypervisor about queued I/O. Secondly, virtqueue_notify() will cause world switch and it may take long time on some hypervisors(such as, qemu-arm), so it isn't good to hold the lock and block other vCPUs. On arm64 quad core VM(qemu-kvm), the patch can increase I/O performance a lot with VIRTIO_RING_F_EVENT_IDX

Hi, I am having problems with file locks with my NFS mounted Maildir setup. NFS Client/IMAP Server is RHEL3 clone whitebox and NFS server is a Fedora Core 2 system. Both are running lockd as far as I can tell. dovecot is installed with Dag's latest dovecot RPMs for RHEL3. Time is synced between the two systems. Here is the pertinent log file entry dovecot: Dovecot starting up Apr 7

On Fri, May 30, 2014 at 11:19 AM, Jens Axboe <axboe at kernel.dk> wrote: > On 2014-05-29 20:49, Ming Lei wrote: >> >> Firstly, it isn't necessary to hold lock of vblk->vq_lock >> when notifying hypervisor about queued I/O. >> >> Secondly, virtqueue_notify() will cause world switch and >> it may take long time on some hypervisors(such as,

On Fri, May 30, 2014 at 11:19 AM, Jens Axboe <axboe at kernel.dk> wrote: > On 2014-05-29 20:49, Ming Lei wrote: >> >> Firstly, it isn't necessary to hold lock of vblk->vq_lock >> when notifying hypervisor about queued I/O. >> >> Secondly, virtqueue_notify() will cause world switch and >> it may take long time on some hypervisors(such as,

Hi I'm currently debugging some replication issues between two dovecot 2.3.9.2 servers, where one is live and the other is just a copy used for backup with no imap user access. After initial alignment (with various error messages such as the stalled io messages a fnctl lock messages) I am seeing replication miss messages or stop altogether on mailboxes, even with no further error messages.

Am Dienstag, 13. Januar 2015, 21:40:34 schrieb Nick Edwards: > On 1/13/15, Michael Schwartzkopff <ms at sys4.de> wrote: > > Hi, > > > > I did some experiments with dovecot on a glusterfs on the active nodes > > without > > a director. So I had concurrent access to the files. > > > > With the help of the available documentation about NFS and

Hi, I've tried to compile 3.0.22 on HPUX 10.20 and get the following error msg: No options are used when running 'configure'. checking configure summary ERROR: No locking available. Running Samba would be unsafe configure: error: summary failure. Aborting config ****** The server details: [qhus029@HP-UX]>uname -a HP-UX qhus029 B.10.20 A 9000/898 1684683361 two-user license

Hi Olly, I tried to reach you through Github notifications(email) about this issue but with no reply, so I thought we could discuss this issue here, I saw three critical problems in the last patch. 1. Adding code to wrong '#if', i added it to else branch 2. Figuring out 'fd', holding the lock and 'fnm' as in windows 'fnm' differs Help me out here, and Mention

Time stamps are correct and my system time is correct. I am now tried to use Sys.setFileTime() to update time stamps as proposed. This does not help. The windows and debian builds give different reports on the time stamp issue. https://win-builder.r-project.org/incoming_pretest/eurostat_3.2.8_20180920_122655/Windows/00check.log

Dear developers, Upon CRAN submission I have bumped into "future file timestamps" warning that I can't solve. I have updated the package as usual, and all checks go through in my system. CRAN reports the following warning however. * checking for future file timestanps ... WARNING Files with future time stamps: DESCRIPTION NAMESPACE README.md The build log is at

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz http://dovecot.org/releases/dovecot-1.0.rc21.tar.gz.sig Just one fix. Maybe the one big thing in Dovecot v2.0.* will be a test suite, which is run before any release. :) - Cache file handling could have crashed rc20 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type:

Hi experts, I boot the xen4.0.0 with gpxe and boot xen 32 bit works well but when I try boot xen 64 bit, the error happens (XEN)Brought up 16 cpus (XEN) *** LOADING DOMAIN 0 *** (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) crc error (XEN) **************************************** Can you give me a light? Thanks Lei -- "We learn from failure, not from

Hi experts, I boot the xen4.0.0 with gpxe and boot xen 32 bit works well but when I try boot xen 64 bit, the error happens (XEN)Brought up 16 cpus (XEN) *** LOADING DOMAIN 0 *** (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) crc error (XEN) **************************************** Can you give me a light? Thanks Lei -- "We learn from failure, not from