--On December 10, 2008 10:36:56 AM +1100 Bron Gondwana
wrote:
Wow, this is the thanks I get for doing sanity checks on files, find more
bugs!
This one is due to delayed expunge, plain and simple. Cyrus decides what
cache records to copy during an IMAP COPY command by reading the cache
offset
Patrick Boutilier wrote:
Patrick Boutilier wrote:
Bron Gondwana wrote:
On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
Feb 8 13:33:59 student2 cyr_expire[29242]: IOERROR: reading cache
record for user.wooddm: got bogus offset 0 for 68/3; try reconstruct
Feb 8 13:33:59 stu
Patrick Boutilier wrote:
Bron Gondwana wrote:
On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
Feb 8 13:33:59 student2 cyr_expire[29242]: IOERROR: reading cache
record for user.wooddm: got bogus offset 0 for 68/3; try reconstruct
Feb 8 13:33:59 student2 cyr_expire[29242]: f
Bron Gondwana wrote:
> On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
>> Feb 8 13:33:59 student2 cyr_expire[29242]: IOERROR: reading cache
>> record for user.wooddm: got bogus offset 0 for 68/3; try reconstruct
>> Feb 8 13:33:59 student2 cyr_expire[29242]: failure expiring
On Sun, Feb 08, 2009 at 09:41:48PM -0400, Patrick Boutilier wrote:
> Bron Gondwana wrote:
>> So - did you try a reconstruct?
>
> No, I wasn't sure if reconstructing would bring back expunged e-mails or
> not. Plus I had 3893 accounts showing these errors and once cyr_expire
> started working wi
On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
> Feb 8 13:33:59 student2 cyr_expire[29242]: IOERROR: reading cache
> record for user.wooddm: got bogus offset 0 for 68/3; try reconstruct
> Feb 8 13:33:59 student2 cyr_expire[29242]: failure expiring
> user.wooddm: System I/O
Bron Gondwana wrote:
> On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
>> Bron Gondwana wrote:
>>> What are you seeing in your syslog? You do read your syslog, right?
>>> (actually, I don't - it's bloody huge. We have auditlog as well, which
>>> more that doubles its size. On
On Sun, Feb 08, 2009 at 09:01:47PM -0400, Patrick Boutilier wrote:
> Bron Gondwana wrote:
>> What are you seeing in your syslog? You do read your syslog, right?
>> (actually, I don't - it's bloody huge. We have auditlog as well, which
>> more that doubles its size. On the other hand, we have a p
Bron Gondwana wrote:
> On Sun, Feb 08, 2009 at 08:18:44AM -0400, Patrick Boutilier wrote:
>> Bron Gondwana wrote:
>>> Also note: in the event of cache corruption, mailbox_cache_size_detail
>>> returns
>>> zero bytes, which correctly makes append_copy re-parse the message file.
>>> It's
>>> all s
On Sun, Feb 08, 2009 at 08:18:44AM -0400, Patrick Boutilier wrote:
> Bron Gondwana wrote:
>> Also note: in the event of cache corruption, mailbox_cache_size_detail
>> returns
>> zero bytes, which correctly makes append_copy re-parse the message file.
>> It's
>> all shiny :)
>>
>> Wes/Ken - pleas
Bron Gondwana wrote:
> Wow, this is the thanks I get for doing sanity checks on files, find more
> bugs!
>
> This one is due to delayed expunge, plain and simple. Cyrus decides what
> cache
> records to copy during an IMAP COPY command by reading the cache offsets for
> msgno and msgno+1 (or th
Wow, this is the thanks I get for doing sanity checks on files, find more bugs!
This one is due to delayed expunge, plain and simple. Cyrus decides what cache
records to copy during an IMAP COPY command by reading the cache offsets for
msgno and msgno+1 (or the end of the cache file if it's the l
12 matches
Mail list logo
