Re: Did calculating the quota change from 2.3 to 2.5?

2016-12-31 Thread Wolfgang Breyha via Info-cyrus
On 31/12/16 06:17, Bron Gondwana via Info-cyrus wrote: > If your cyrus.* files are identical then you have pretty weird mailboxes, > but yeah - I guess it could happen if you had two folders with identical > messages in identical order and all the timestamps identical. Especially empty mailbox cy

Re: Did calculating the quota change from 2.3 to 2.5?

2016-12-30 Thread Bron Gondwana via Info-cyrus
On Sat, 31 Dec 2016, at 10:57, Wolfgang Breyha via Info-cyrus wrote: > On 29/11/16 22:37, Jason L Tibbitts III via Info-cyrus wrote: > > Fun random question: Does anything blow up if you run hardlink on your > > mail spool? (The hardlink program finds identical files and hardlinks > > them.) > >

Re: Did calculating the quota change from 2.3 to 2.5?

2016-12-30 Thread Wolfgang Breyha via Info-cyrus
On 29/11/16 22:37, Jason L Tibbitts III via Info-cyrus wrote: > Fun random question: Does anything blow up if you run hardlink on your > mail spool? (The hardlink program finds identical files and hardlinks > them.) Using "hardlink" is IMO not save on imap spools since it also links cyrus.* files

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-30 Thread Adam Tauno Williams via Info-cyrus
> > If you use imapsync, it doesn't know about that, and will upload > > the same message twice. 2.5 doesn't have the smarts to recognise > > that it's the same message. > imapsync can only sync mail the old server knows about. And in the > end there is more quota used on the new server!? > The onl

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-30 Thread Marc Patermann via Info-cyrus
Bron, Am 29.11.2016 um 22:18 Uhr schrieb Bron Gondwana: Quota is a sum of byte sizes of raw unexpunged messages. It doesn't deduplicate. Likely issue is incorrect quota_mailbox_used in the cyrus.index header on 2.3. a reconstruct will fix those, then quota -f again. Does not change anything.

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-29 Thread Bron Gondwana via Info-cyrus
On Wed, 30 Nov 2016, at 08:37, Jason L Tibbitts III via Info-cyrus wrote: > > "BG" == Bron Gondwana via Info-cyrus > > writes: > > BG> If you use imapsync, it doesn't know about that, and will upload the > BG> same message twice. 2.5 doesn't have the smarts to recognise that > BG> it's t

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-29 Thread Jason L Tibbitts III via Info-cyrus
> "BG" == Bron Gondwana via Info-cyrus > writes: BG> If you use imapsync, it doesn't know about that, and will upload the BG> same message twice. 2.5 doesn't have the smarts to recognise that BG> it's the same message. Fun random question: Does anything blow up if you run hardlink on yo

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-29 Thread Bron Gondwana via Info-cyrus
Quota is a sum of byte sizes of raw unexpunged messages. It doesn't deduplicate. Likely issue is incorrect quota_mailbox_used in the cyrus.index header on 2.3. a reconstruct will fix those, then quota -f again. It's not related to du. The problem with imapsync is that it doesn't handle single i

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-29 Thread Marc Patermann via Info-cyrus
Bron, Am 29.11.2016 um 13:26 Uhr schrieb Bron Gondwana via Info-cyrus: No, the quota calculations are identical. It's possible that your quota was incorrectly calculated on the source server though. A quota -f there should correct the calculations. unluckily it does not. quota -f on seems no

Re: Did calculating the quota change from 2.3 to 2.5?

2016-11-29 Thread Bron Gondwana via Info-cyrus
No, the quota calculations are identical. It's possible that your quota was incorrectly calculated on the source server though. A quota -f there should correct the calculations. Regards, Bron. On Tue, 29 Nov 2016, at 01:36, Marc Patermann via Info-cyrus wrote: > Hi, > > while migrating from