Re: qmail-ldap and GFS

David Rodríguez Fernández <[email protected]> Wed, 3 Nov 2010 19:43:29 +0100
Newsgroups gmane.mail.qmail.ldap
Message-ID <[email protected]>
Hi, You can have performace problems with the io/s from your filesystem, is
a problem inherent to hardware (disk and network).
I have a similar escenario with all mailboxes in a NFS server. In my setup
the filesystem is over a SAN disk distributed over a great numbre of disks
with lvm and the nfs server have ethernet cards with 10G in a 802.3ad
bonding. This setup have H.A. with heartbeat with other node as backup. This
is an older setup and I only have changed the hardware, but I'm thinking
make a H.A. active-active with two options:
One similar to you with gfs or oraclefs
And other creating two nfs shares (one for every nfs server), with the user
distributed over the two shares, and one server acting as backup of the
other.

In my actual config I don't have any problem. Only a clue, don't use
reiserfs for NFS exported filesystem, was my error.

On Wed, Nov 3, 2010 at 16:25, Ibrahim Harrani <[email protected]>wrote:

> Hi,
>
> Currently, my domains and users are distributed to different mailhosts in
> my qmail ldap cluster.
> In this setup, If I one of the mailhost is down, the users can't access to
> mailbox on this server.
> To setup a redundant system,  I would like to keep mailbox on GFS file
> system with multiple backends.
> All backends will share the same GFS partition. There will be one mailhost
> entry in openldap entries and
> load balancer to distrube pop3/imap and smtp connections to backends. If
> one of the backend is down, this will not effect
> the users.
>
> But, I have some doubts about locks and I/O issues. Can you please share
> your experience about this kind of setup?
>
> Thanks
>
>


-- 
POR FAVOR, si reenvia este correo, tenga en cuenta lo siguiente:
1.- Borre la dirección del remitente así como cualquier otra dirección que
aparezca en el cuerpo del mensaje.
2.- Proteja las direcciones de los destinatarios colocando las mismas en la
línea de CCO (CON COPIA OCULTA)

Combatir el spam es tarea de todos.