On Wed, Apr 03, 2013 at 03:53:58PM -0500, Sam Lang wrote: > On Thu, Mar 28, 2013 at 6:32 AM, Kai Blin <kai@xxxxxxxxx> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 2013-03-28 09:16, Volker Lendecke wrote: > >> On Wed, Mar 27, 2013 at 10:43:36PM -0700, Matthieu Patou wrote: > >>> On 03/27/2013 10:41 AM, Marco Aroldi wrote: > >>>> Hi list, I'm trying to create a active/active Samba cluster on > >>>> top of Cephfs I would ask if Ceph fully supports CTDB at this > >>>> time. > >>> If I'm not wrong Ceph (even CephFS) do not support exporting a > >>> block device or mounting the same FS more than once whereas CTDB > >>> explicitly require that you have a distributed filesystem where > >>> the same filesystem is mounted across all the nodes. > >> > >> Is that true? I thought Ceph was one of the cluster filesystems > >> doing just that. What is Ceph if not a cluster file system? > > > > There's some problem with mounting the in-kernel cephfs driver on > > systems running the osd, iirc. I had to use the fuse-based driver to > > mount, which obviously is not too great, speed-wise. > > See http://ceph.com/docs/master/faq/#try-ceph for a better description > > of the issue. > > Just to let folks know, we have a ceph vfs driver for samba that we > are testing out now. We're planning to resolve a few of the bugs that > we're seeing presently with smbtorture, and send a pull request to the > samba repo. If anyone wants to help with testing, let us know. The > changes currently reside in the ceph branch of > http://github.com/ceph/samba. Does the libceph have an async API ? If we could plug it into the Samba async VFS pread_send/pwrite_send API you'd get much better performance. If libceph is thread-safe you could create your own modified version of vfs_aio_pthread() that called the ceph backend (although you'll need the ability to set credentials into the ceph userspace calls to cope with seteuid changes). Jeremy. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
