3 ms·
Samba ships with modules for ceph, gluster and gpfs. Here's the info you need: https://documentation.suse.com/ses/6/html/ses-all/cha-ses-cifs.html https://doc
by jra_samba 5y ago
Samba ships with modules for ceph, gluster and gpfs.
Here's the info you need:
https://documentation.suse.com/ses/6/html/ses-all/cha-ses-cifs.html https://documentation.suse.com/ses/6/html/ses-all/cha-ses-ci...
Note the share definition:
[SHARE_NAME]
path = /
vfs objects = ceph
ceph: config_file = /etc/ceph/ceph.conf
ceph: user_id = samba.gw
read only = no
kernel share modes = no
The "vfs objects = ceph" is the important part.
(if you're only exporting via Samba you can safely leave leases/oplocks enabled).
- tinco 5y agoI was wrong, I'm not using fuse, but instead the kernel cephfs implementation. That article considers vfs_ceph to be legacy, and instead recommends to use the regular mount, but then does recommend to install samba-ceph and gives a configuration that does not mention ceph at all. What does the samba-ceph package do if you're not mentioning ceph in the configuration, does samba detect the filesystem is mounted through ceph act accordingly? I guess I should just try both approaches and see which one performs best.
- jra_samba 5y agoTry using the "legacy" method, just to ensure you can get it working. Using "vfs objects = ceph" causes Samba to load a custom VFS module that translates SMB1/2/3 requests -> Samba VFS -> cephfs calls. That's why the share sets "path = /" (as it's not a local path) and then redirects all filesystem access via vfs_ceph.