--On 31. Mai 2009 22:41:52 +1000 Bron Gondwana wrote:
I interpret the "System I/O error" to be the IOERROR from the line
before, i.e. not actually an I/O error but rather a corrupt file. The
error does not show on any of the previous days, nor does it show today.
Sounds to me like it was copy
On Sun, May 31, 2009 at 10:53:14AM +0200, Sebastian Hagedorn wrote:
> -- "Ciprian Marius Vizitiu (GBIF)" is rumored to have
>> I for one 'd worry more about that "System I/O error ". It can be that
>> there was a storage error which didn't happen during a second attempt.
Nah, it's called an "IOE
-- "Ciprian Marius Vizitiu (GBIF)" is rumored to have
mumbled on 31. Mai 2009 09:27:41 +0200 regarding Re: Self-healing mailbox?:
What gives? Can I assume that the error from yesterday somehow healed
itself? Or should I run reconstruct anyway?
I for one 'd worry more about t
Sebastian Hagedorn wrote:
> Today I noticed the following in our Logwatch script's output for
> Cyrus (2.3.14):
>
> May 30 04:51:06 lvr13 cyr_expire[562]: failure expiring user.aqg04:
> System I/O error
>
> May 31 04:46:40 lvr13 cyr_expire[28829]: Expunged 7 messages from
> user.aqg04
>
> What g
Today I noticed the following in our Logwatch script's output for Cyrus
(2.3.14):
May 30 04:51:06 lvr13 cyr_expire[562]: IOERROR: reading cache record for
user.aqg04: initial bogus offset 11091472 of 75256 for 6/10; mailbox needs
a reconstruct
May 30 04:51:06 lvr13 cyr_expire[562]: failure exp
