Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#68565 - [samba] Missing GlusterFS VFS module
Attached to Project:
Arch Linux
Opened by Andrea (andry) - Sunday, 08 November 2020, 14:37 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 30 March 2022, 14:38 GMT
Opened by Andrea (andry) - Sunday, 08 November 2020, 14:37 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 30 March 2022, 14:38 GMT
|
DetailsAs of samba 4.13.2-1, the package lacks the GlusterFS VFS module (/usr/lib/samba/vfs/glusterfs.so) which is used to improve read and write performance with Gluster volumes.
Samba's man pages include an example on how the module would be used: https://www.samba.org/samba/docs/current/man-html/vfs_glusterfs.8.html There is a simple fix though: just add "glusterfs" to the makedepends of the PKGBUILD for samba. After that, the configure step will correctly find the Gluster libraries and allow the compilation of the VFS. The module doesn't do anything if it isn't directly used in a share definition (see the man page linked above), so it won't break existing users. The package correctly builds on x86_64 (under Docker; I'll test it under a VM as soon as I have some free time) and ARMv7h. Tested from samba 4.11.x through 4.13.2. Keep in mind that this module is fundamentally different from vfs_glusterfs_fuse (/usr/lib/samba/vfs/glusterfs_fuse.so). |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 30 March 2022, 14:38 GMT
Reason for closing: Fixed
Additional comments about closing: 4.16.0-4
Wednesday, 30 March 2022, 14:38 GMT
Reason for closing: Fixed
Additional comments about closing: 4.16.0-4
Comment by Oleksandr Natalenko (post-factum) -
Tuesday, 06 April 2021, 11:38 GMT
Any news on this report please? Thanks!
Comment by Oleksandr Natalenko (post-factum) -
Thursday, 08 April 2021, 13:41 GMT
FWIW, also tested on 4.14.2, and it works fine.