Clustering Samba with GlusterFS with Backend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> Understand that Samba's Share Lock and Byte Range Lock is very depend on the
> inode on disk, so I need to make sure the inode number across the cluster
> disk must be same.
> Senario 1, I use AFR translator, I use stat command to check the inode
> number of a file, it show me a different number of inode on different
> client. Senario 2, I use distribute, result is same with different inode
> number.
>
> Only workable translator is Unify which the device id and inode number is
> same on client 1, client 2, client .....
> So the only workable Translator is Unify, but also understand that Unify
> have some performace issue, will Distribute translator replace Unify? Or is
> that any method to have consistent device id and inode across cluster disk?

Recent versions of Distribute return the same inode number
consistently on all clients. Please upgrade.

> Another question is how can I get Posix ACL support with GlusterFS?

Currently Posix ACL is not supported

Avati



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux