On Sep 30, 2012, at 1:36 PM, Bron Gondwana wrote:
> On Sun, Sep 30, 2012, at 09:46 PM, Eric Luyten wrote:
>> On Sun, September 30, 2012 6:47 pm, Bryan Hill wrote:
>>
>> <...>
>>> Sorry for hi-jacking this thread, but I'm curious as to the preferred method
>>> of forcing a reindex on a mailbox?
On Sun, Sep 30, 2012, at 09:46 PM, Eric Luyten wrote:
> On Sun, September 30, 2012 6:47 pm, Bryan Hill wrote:
>
> <...>
> > Sorry for hi-jacking this thread, but I'm curious as to the preferred method
> > of forcing a reindex on a mailbox? I know it triggers when a user logs in
> > and accesses t
On Sun, September 30, 2012 6:47 pm, Bryan Hill wrote:
<...>
> Sorry for hi-jacking this thread, but I'm curious as to the preferred method
> of forcing a reindex on a mailbox? I know it triggers when a user logs in
> and accesses the mailbox. I would like to divide up users and perform the
> rei
On Sep 25, 2012, at 11:57 AM, Deniss wrote:
>
>
> On 25.09.2012 15:28, Eric Luyten wrote:
>> On Tue, September 25, 2012 2:01 pm, Sebastian Hagedorn wrote:
>>> Hi,
>>>
>>>
>>> about three weeks ago we upgraded our Cyrus installation from 2.3.x to
>>> 2.4.16.
>>> We were aware of the reindexi
Hi Eric,
--On 25. September 2012 14:28:03 +0200 Eric Luyten
wrote:
Thank you for sharing your experiences.
As a site willing/needing to upgrade from 2.3.16 to 2.4.X this fall, we
are interested in learning about your storage backend characteristics.
What read/write IOPS rates were you regi
Simon Matter wrote, on 26.09.2012 06:58:
> I have not used freedup for restoring the hardlinks but I'm interested in
> the patch. If it's not big could you post it here?
Sure! attached.
I built a RPM based on
http://pkgs.repoforge.org/freedup/freedup-1.5.3-1.rf.src.rpm
and latest source.
But buil
On 2012.09.26. 10:24, Sebastian Hagedorn wrote:
> Hi,
>
> I've got questions regarding the procedure you describe. I'm trying to
> wrap my head around the various possible approaches to replication and
> clustering.
>
> --On 25. September 2012 21:57:49 +0300 Deniss wrote:
>
>> migration proces
Hi,
I've got questions regarding the procedure you describe. I'm trying to wrap
my head around the various possible approaches to replication and
clustering.
--On 25. September 2012 21:57:49 +0300 Deniss wrote:
migration process from 2.3 to 2.4 took ~ one year for our installation.
we conv
--On 26. September 2012 09:42:17 +0300 Janne Peltonen
wrote:
As it happened, we didn't have any trouble with the reconstruction of any
mailboxes, the process went flawlessly - it was just slow.
Same here.
Also, it did
cause observable slowness only because at first, I hadn't reconstructed
Hi!
On Tue, Sep 25, 2012 at 05:55:27PM +0200, Wolfgang Breyha wrote:
> Time was not the limiting factor for us. Availability and safety of our
> mailboxes was. Nobody can guarantee you that the migration works out
> flawlessly. If moving one mailbox fails I have troubles with exactly one
> mailbox
On Wed, Sep 26, 2012, at 01:25 AM, Wolfgang Breyha wrote:
> On 2012-09-25 19:05, Simon Beale wrote:
> > The only gotcha I experienced was I forgot that cyrus was configured to
> > hardlink mail, which of course was no longer the case after each mailbox
> > was migrated, so my disk usage exploded. (
> On 2012-09-25 19:05, Simon Beale wrote:
>> The only gotcha I experienced was I forgot that cyrus was configured to
>> hardlink mail, which of course was no longer the case after each mailbox
>> was migrated, so my disk usage exploded. (But easily fixed/restored once
>> identified).
>
> What did y
On 2012-09-25 19:05, Simon Beale wrote:
> The only gotcha I experienced was I forgot that cyrus was configured to
> hardlink mail, which of course was no longer the case after each mailbox
> was migrated, so my disk usage exploded. (But easily fixed/restored once
> identified).
What did you use fo
On 25.09.2012 15:28, Eric Luyten wrote:
> On Tue, September 25, 2012 2:01 pm, Sebastian Hagedorn wrote:
>> Hi,
>>
>>
>> about three weeks ago we upgraded our Cyrus installation from 2.3.x to
>> 2.4.16.
>> We were aware of the reindexing issue, so we took precautionary
>> measures, but they didn'
> Hi!
>
> On Tue, Sep 25, 2012 at 03:25:45PM +0200, Wolfgang Breyha wrote:
>> Sebastian Hagedorn wrote, on 25.09.2012 14:01:
>> > I realize that some of our problems were caused by infrastructure
>> that's
>> > not up to current standards, but nonetheless I would really urge you
>> to
>> > never ag
Janne Peltonen wrote, on 25.09.2012 15:34:
> Could you elaborate on that? I considered that option, but seeing as moving
> even a couple dozen users from a backend to another using RENAME takes hours
> and one backend contains thousands of users, I decided to just live with the
> ~1
> day of unbea
Hi!
On Tue, Sep 25, 2012 at 03:25:45PM +0200, Wolfgang Breyha wrote:
> Sebastian Hagedorn wrote, on 25.09.2012 14:01:
> > I realize that some of our problems were caused by infrastructure that's
> > not up to current standards, but nonetheless I would really urge you to
> > never again use an up
Sebastian Hagedorn wrote, on 25.09.2012 14:01:
> I realize that some of our problems were caused by infrastructure that's
> not up to current standards, but nonetheless I would really urge you to
> never again use an upgrade mechanism like that. Give admins a chance to
> upgrade indexes in the b
Can you tell us more about your storage configuration?
Ben
--
Ben Carter
University of Pittsburgh/CSSD
b...@pitt.edu
412-624-6470
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mai
On Tue, September 25, 2012 2:01 pm, Sebastian Hagedorn wrote:
> Hi,
>
>
> about three weeks ago we upgraded our Cyrus installation from 2.3.x to 2.4.16.
> We were aware of the reindexing issue, so we took precautionary
> measures, but they didn't help a lot. We've got about 7 TB of mail data for
>
Hi,
about three weeks ago we upgraded our Cyrus installation from 2.3.x to
2.4.16. We were aware of the reindexing issue, so we took precautionary
measures, but they didn't help a lot. We've got about 7 TB of mail data for
almost 200,000 mailboxes. We did the upgrade on a Sunday and had told o
21 matches
Mail list logo
