[Gluster-devel] Problem with samba/ctdb (clustered samba)

[Amar S. Tumballi]

Hi JR,

 As you said, two glusterfs exports (different process) would solve it. But
yes, its bit complex to maintain.

Meanwhile, if most part of your clients don't use locks, then posix-locks
will act as an dummy layer. It comes into act only when a fnctl()/flock()
calls are made. So, I think you can just use posix-locks translator in the
current glusterfsd process.

Regards,
Amar

On Mon, Jun 2, 2008 at 9:56 AM, jrs <botemout at gmail.com> wrote:

> Hi gents,
>
> I'm trying to serve up gluster to a large set of
> windows clients using samba and it's clustering
> extension, CTDB.
>
> CTDB requires that samba's secrets.tdb file (among
> others) be available to all nodes in the cluster.
> It turns out that locking is done by each node
> when writing to the file.
>
> This means that I need some storage in gluster where
> I can apply the posix-locks translator.  Problem is
> I don't want it on for most of my storage.
>
> Is there a convenient way to just have posix-locks on
> for a given sub-directory of an already defined brick?
>
> If not, and I have to have a separate brick to apply
> posix-locks to then how do I access this directory?
> Of course, the way I'm running glusterfsd is to
> give a mount point as the last argument.
>
> How do I handle this?
>
> Do I just have to run two different glusterfsd processes?
>
> thanks much,
>
> JR
>
>
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at nongnu.org
> http://lists.nongnu.org/mailman/listinfo/gluster-devel
>



-- 
Amar Tumballi
Gluster/GlusterFS Hacker
[bulde on #gluster/irc.gnu.org]
http://www.zresearch.com - Commoditizing Super Storage!