Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-25 Thread Jeff Gustafson
On Mon, 2012-06-25 at 19:54 +0300, Timo Sirainen wrote: > On 25.6.2012, at 19.49, Charles Marcus wrote: > > I'd suggest you try again with 2.1.7... > > The rewritten dsync is in v2.2 tree. v2.1's dsync is a fixed version > of v2.0's dsync. I have no idea why v2.1's dsync would be less > reliable t

Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-25 Thread Timo Sirainen
On 25.6.2012, at 19.49, Charles Marcus wrote: >> I did try the 2.1.x version of dsync back in March. I found the version >> to be very unreliable. It would crash with many types of operations >> (e.g. maildir -> mdbox conversions). > > Well, the version in 2.0.x was problematic, which is why Tim

Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-25 Thread Charles Marcus
On 2012-06-25 12:45 PM, Jeff Gustafson wrote: On Sat, 2012-06-23 at 06:29 -0400, Charles Marcus wrote: # 2.0.13: /etc/dovecot/dovecot.conf As you are aware (since you participated in the thread discussion about this months ago), Timo is working on a total rewrite of dsync, and if memory serv

Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-25 Thread Jeff Gustafson
On Sat, 2012-06-23 at 06:29 -0400, Charles Marcus wrote: > > > > # 2.0.13: /etc/dovecot/dovecot.conf > > As you are aware (since you participated in the thread discussion about > this months ago), Timo is working on a total rewrite of dsync, and if > memory serves, it is mainly for 2.1+, and i

Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-23 Thread Charles Marcus
On 2012-06-22 5:24 PM, Jeff Gustafson wrote: I'm getting an error backing up mailboxes. I'm using the mirror command: dsync -fvo mail_home=/home/users/bob mirror ssh vmail@10.1.4.1 dsync -o mail_home=/home/.incoming_mail_migrations/users/bob # 2.0.13: /etc/dovecot/dovecot.conf As you are

Re: [Dovecot] dsync error: "Mailboxes don't have unique GUIDs"

2012-06-22 Thread Doug Henderson
Hey, just a point of clarification. In at least some of the cases (possibly all, I'll leave that up to Jeff to state) an initial dsync (as documented in Jeff's message) was completed successfully and the problem occurred when we ran a second (using exactly the same cmd) time to catch any change