similar to: Error: Corrupted dbox file

Thanks Jack. That's good to know. It is definitely something to consider. In a distributed storage scenario we might build a dedicated pool for that and tune the pool as more capacity or performance is needed. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Wed, May 16, 2018 at 4:45 PM Jack <ceph at jack.fr.eu.org> wrote:

Hello Jack, yes, I imagine I'll have to do some work on tuning the block size on cephfs. Thanks for the advise. I knew that using mdbox, messages are not removed but I though that was true in sdbox too. Thanks again. We'll soon do benchmarks of sdbox vs mdbox over cephfs with bluestore backend. We'll have to do some some work on how to simulate user traffic, for writes and readings.

Hi, some time back we had similar discussions when we, as an email provider, discussed to move away from traditional NAS/NFS storage to Ceph. The problem with POSIX file systems and dovecot is that e.g. with mdbox only around ~20% of the IO operations are READ/WRITE, the rest are metadata IOs. You will not change this with using CephFS since it will basically behave the same way as e.g. NFS. We

I'm sending this message to both dovecot and ceph-users ML so please don't mind if something seems too obvious for you. Hi, I have a question for both dovecot and ceph lists and below I'll explain what's going on. Regarding dbox format (https://wiki2.dovecot.org/MailboxFormat/dbox), when using sdbox, a new file is stored for each email message. When using mdbox, multiple

Hi! 2.2.35 is not unstable, but apparently it is in debian distribution, which is called 'unstable'. Aki On 27.04.2018 06:16, Webert de Souza Lima wrote: > Got 2.2.34 running using debian strech image + strech-backports repos! > > > Regards, > > Webert Lima > DevOps Engineer at MAV Tecnologia > *Belo Horizonte - Brasil* > *IRC NICK - WebertRLZ* > > On

Hey Aki Tuomi, how are you doing? I have tried many ways for getting 2.2.35 pre-built installed via 'apt-get install' in Debian Jessie and Stretch using the official repos. The reason I prefer to install pre-built instead of compiling it is because the I run it on dockers, so it's a lot easier and automated to just apt-get install it. I was using 2.2.31 devel in Debian Jessie, I

Got 2.2.34 running using debian strech image + strech-backports repos! Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Thu, Apr 26, 2018 at 9:37 PM, Webert de Souza Lima <webert.boss at gmail.com > wrote: > Oh thank you Cedric, I hadn't check that. So 2.2.35 is unstable, huh? > I'll deploy 2.2.34 instead. > >

Hi, I came across the 'CTDB_CAPABILITY_LMASTER=no' and 'CTDB_CAPABILITY_RECMASTER=no' options in my quest to salvage a rather poorly performing CTDB cluster over Ceph(fs). Unfortunately, the docs provide not enough information for a clustering noop like myself. Would there be any benefit to disabling those options for a branch office node on a high-latency WAN connection?

Oh thank you Cedric, I hadn't check that. So 2.2.35 is unstable, huh? I'll deploy 2.2.34 instead. Thank you! Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Thu, Apr 26, 2018 at 7:51 PM, Cedric M <cedric.malitte at gmail.com> wrote: > Hi, > did you check in unstable ? > https://tracker.debian.org/pkg/dovecot

Hi, did you check in unstable ? https://tracker.debian.org/pkg/dovecot 2018-04-26 16:43 GMT-04:00 Webert de Souza Lima <webert.boss at gmail.com>: > hmm I think I should use stretch instead of jessie, OR I should use a > stretch-backport repos, right? > > > Regards, > > Webert Lima > DevOps Engineer at MAV Tecnologia > *Belo Horizonte - Brasil* > *IRC NICK -

seems that you want your others services to depend on tinc, and not to set tinc to stop after the network has stopped On Wednesday, 24 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > On many systems (Debian Jessie, Tinc 1.1 from git) using unit file > provided in git, I can see that when I "reboot", Tinc seems to stop > before others

hmm I think I should use stretch instead of jessie, OR I should use a stretch-backport repos, right? Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Thu, Apr 26, 2018 at 5:39 PM, Webert de Souza Lima <webert.boss at gmail.com > wrote: > Hi, I can't figure how to install latest stable dovecot version 2.2.35 in > Debian

You could remove them with sieve in the latest version of pigeonhole. On Mar 24, 2015 7:33 AM, Florent B <florent at coppint.com> wrote: > > I know about RFC's, but that could be an option, not enabled by default.

Thank you for your report, we'll look into it! Aki > On December 27, 2017 at 8:16 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > This repository does not work with Aptly. > It seems "architecture" line is wrong in InRelease file (needs to be > "Architectures:" instead of "Architecture:"). > And

> On October 20, 2017 at 12:37 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > We use Dovecot packages from http://xi.dovecot.fi/debian/. > > Could it be possible to serve it with HTTPS ? > > Thank you. > > Florent Hi! It has now https enabled with valid certificate. Aki

On Mon, Dec 7, 2015 at 7:20 PM, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I already posted about this issue, but I can't find the old thread. > > I have a cluster of 5 nodes, running Proxmox 4, and Tinc as "virtual > switch" for my nodes : on each node, a bridge "vmbr1" where Tinc is > connected, provides me a secured network

why dont you place a service dependency on your tinc service init/systemd files to depend on your fuse/mount service? On Tuesday, 23 August 2016, Florent B <florent at coppint.com> wrote: > Hi everyone, > > I have a special setup were hosts files of Tinc are stored in a > directory mounted by fuse and shared across my hosts (Proxmox /etc/pve). > > On boot, sometimes Tinc

Try to disable ExperimentalProtocol. Florent B <florent at coppint.com> 于2018年8月10日周五 下午9:16写道： > > Hi, > > Is it possible to completely disable encryption with Tinc 1.1 ? > > I set in my configuration : > > ExperimentalProtocol = no > Cipher = none > Digest = none > > But it does not seem to disable encryption (same performance). > > Is it possible

It's not. In fact it's explicitly telling you that it's *not* forwarding. On 22 December 2015 at 15:55, Florent B <florent at coppint.com> wrote: > Hi, > > I have a lot of messages like this in my Tinc 1.1-git log : > > Sending packet from host5 (MYSELF port 655) to host4 (192.168.0.4 port > 655) via host4 (192.168.0.4 port 655) (UDP) > > Is it expected ?

This smells like https://github.com/gsliepen/tinc/pull/104 - are you sure you're using latest HEAD? How often does this occur? Does it correlate with other events such as nodes joining or leaving? Does it occur more often if you reduce the value of KeyExpire? On 22 December 2015 at 16:10, Florent B <florent at coppint.com> wrote: > Hi, > > With latest Tinc 1.1 git code, I have