Discussion:
[Gluster-users] vfs_gluster broken
Terry McGuire
2018-09-11 21:10:52 UTC
Permalink
Hello list. I had happily been sharing a Gluster volume with Samba using vfs_gluster, but it has recently stopped working right. I think it might have been after updating Samba from 4.6.2 to 4.7.1 (as part of updating CentOS 7.4 to 7.5). The shares suffer a variety of weird issues, including:

- sporadic connection refusals (credentials are accepted as valid, but volume is unavailable)
- on Mac, when attempting to write a file: "The operation can’t be completed because an unexpected error occurred (error code -50)."
- on Windows, sometimes when writing and sometimes when reading: "Z:\ is not accessible. The parameter is incorrect"
-on Mac and Windows, the contents of the volume in Finder/Explorer windows sometimes disappears, sometimes reappearing later, sometimes not.
- on Mac (and similar on Windows), volume icon sometimes disappears - maybe the volume unmounts, but it's unclear.

All these issues vanish when I switch to sharing the FUSE-mounted volume, but, of course, I lose the advantages of vfs_gluster.

My gluster version initially was 3.10.12. I’ve since updated to gluster 3.12.13, but the symptoms are the same.

Does this sound familiar to anyone?

Regards,
Terry

_____________________________
Terry McGuire
Information Services and Technology (IST)
University of Alberta
Edmonton, Alberta, Canada T6G 2H1
Phone: 780-492-9422
Anoop C S
2018-09-12 05:42:47 UTC
Permalink
Post by Terry McGuire
Hello list. I had happily been sharing a Gluster volume with Samba using vfs_gluster, but it has
recently stopped working right. I think it might have been after updating Samba from 4.6.2 to
4.7.1 (as part of updating CentOS 7.4 to 7.5). The shares suffer a variety of weird issues,
- sporadic connection refusals (credentials are accepted as valid, but volume is unavailable)
Does that mean after authentication share is not at all listed?
Post by Terry McGuire
- on Mac, when attempting to write a file: "The operation can’t be completed because an unexpected
error occurred (error code -50)."
How is this write performed? via Finder or via command-line?
Post by Terry McGuire
- on Windows, sometimes when writing and sometimes when reading: "Z:\ is not accessible. The
parameter is incorrect"
How is this write performed? via Explorer or Powershell?
Post by Terry McGuire
-on Mac and Windows, the contents of the volume in Finder/Explorer windows sometimes disappears,
sometimes reappearing later, sometimes not.
- on Mac (and similar on Windows), volume icon sometimes disappears - maybe the volume unmounts,
but it's unclear.
Is this a clustered Samba setup i.e, with CTDB for high availability?
Post by Terry McGuire
All these issues vanish when I switch to sharing the FUSE-mounted volume, but, of course, I lose
the advantages of vfs_gluster.
Can you please attach the output of `testparm -s` so as to look through how Samba is setup?
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated to gluster 3.12.13, but the symptoms
are the same.
Does this sound familiar to anyone?
All mentioned symptoms point towards a disconnection. We need to find out the origin of this
disconnection. What do we have in logs under /var/log/samba/? Any errors?
Post by Terry McGuire
Regards,
Terry
_____________________________
Terry McGuire
Information Services and Technology (IST)
University of Alberta
Edmonton, Alberta, Canada T6G 2H1
Phone: 780-492-9422
_______________________________________________
Gluster-users mailing list
https://lists.gluster.org/mailman/listinfo/gluster-users
Terry McGuire
2018-09-12 16:37:17 UTC
Permalink
This post might be inappropriate. Click to display it.
Anoop C S
2018-09-14 08:32:18 UTC
Permalink
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Hello list. I had happily been sharing a Gluster volume with Samba using vfs_gluster, but it
has
recently stopped working right. I think it might have been after updating Samba from 4.6.2 to
4.7.1 (as part of updating CentOS 7.4 to 7.5). The shares suffer a variety of weird issues,
- sporadic connection refusals (credentials are accepted as valid, but volume is unavailable)
Does that mean after authentication share is not at all listed?
On a Mac, after the auth dialog disappears (suggesting the auth was valid), a dialog appears
saying the volume is unavailable. Can’t recall what the behaviour on Windows is, but it would be
equivalent. (This error doesn’t happen often, so I can’t quickly reproduce it, and I can’t even
quite be sure it’s related to this problem, but I suspect it is.)
Post by Anoop C S
Post by Terry McGuire
- on Mac, when attempting to write a file: "The operation can’t be completed because an
unexpected
error occurred (error code -50)."
How is this write performed? via Finder or via command-line?
That error appears when using the Finder. It happens pretty much all the time, and is the
clearest symptom of this problem. Using the command-line, anything that attempts I/O with the
Mac:~ root# ls /Volumes/
Macintosh HD module
Mac:~ root# ls -l /Volumes/
ls: module: Invalid argument
total 8
lrwxr-xr-x 1 root wheel 1 24 Aug 15:48 Macintosh HD -> /
Mac:~ root# touch /Volumes/module/test
touch: /Volumes/module/test: Invalid argument
Mac:~ root#
Post by Anoop C S
Post by Terry McGuire
- on Windows, sometimes when writing and sometimes when reading: "Z:\ is not accessible. The
parameter is incorrect"
How is this write performed? via Explorer or Powershell?
Explorer.
Post by Anoop C S
Post by Terry McGuire
-on Mac and Windows, the contents of the volume in Finder/Explorer windows sometimes
disappears,
sometimes reappearing later, sometimes not.
- on Mac (and similar on Windows), volume icon sometimes disappears - maybe the volume
unmounts,
but it's unclear.
Is this a clustered Samba setup i.e, with CTDB for high availability?
Not clustered. Just a plain vanilla Samba.
Post by Anoop C S
Post by Terry McGuire
All these issues vanish when I switch to sharing the FUSE-mounted volume, but, of course, I
lose
the advantages of vfs_gluster.
Can you please attach the output of `testparm -s` so as to look through how Samba is setup?
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[share1]"
Processing section "[share2]"
Processing section "[nomodule]"
Processing section "[nomodule-nofruit]"
Processing section "[module]"
Processing section "[IPC$]"
WARNING: No path in service IPC$ - making it unavailable!
NOTE: Service IPC$ is flagged unavailable.
Loaded services file OK.
idmap range not specified for domain '*'
ERROR: Invalid idmap range for domain *!
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients
results in undefined behaviour.
Server role: ROLE_DOMAIN_MEMBER
# Global parameters
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 50
realm = XXXX.AD.UALBERTA.CA
security = ADS
workgroup = STS
glusterfs:volume = mfs1
idmap config * : backend = tdb
access based share enum = Yes
force create mode = 0777
force directory mode = 0777
include = /mfsmount/admin/etc/mfs/smb_shares.conf
kernel share modes = No
read only = No
smb encrypt = desired
vfs objects = glusterfs
[share1]
path = /share1
[share2]
path = /share2
[nomodule]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects = fruit streams_xattr
[nomodule-nofruit]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects =
[module]
path = /share1
[IPC$]
available = No
vfs objects =
Post by Anoop C S
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated to gluster 3.12.13, but the
symptoms
are the same.
Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?

If GlusterFS was at v3.10.12, are you sure that you were experiencing issues with samba v4.7.1?
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Does this sound familiar to anyone?
All mentioned symptoms point towards a disconnection. We need to find out the origin of this
disconnection. What do we have in logs under /var/log/samba/? Any errors?
[2018/09/12 09:37:17.873711, 0] ../source3/modules/vfs_glusterfs.c:996(vfs_gluster_stat)
glfs_stat(.) failed: Invalid argument
Might be related to https://bugzilla.samba.org/show_bug.cgi?id=13585.

Can you try installing a version of GlusterFS < 3.12.13 and see if it works normally?
Post by Terry McGuire
There appears to be some sort of connection remaining, as I can continue to cause these errors in
the server log by attempting I/O with the share.
This seems like the most promising lead to find the root cause. Hopefully you (or someone) can
interpret what it means, and what I might do about it (besides not using vfs_gluster anymore).
Regards,
Terry
Terry McGuire
2018-09-17 16:31:27 UTC
Permalink
Post by Anoop C S
Post by Terry McGuire
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated to gluster 3.12.13, but the
symptoms
are the same.
Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?
If GlusterFS was at v3.10.12, are you sure that you were experiencing issues with samba v4.7.1?
Definitely 3.10.12. Our production service is still using it:

***@mfs-01 ~]#gluster --version
glusterfs 3.10.12


Definitely samba 4.7.1:

***@mfs-01 ~]#smbstatus --version
Version 4.7.1


As an experiment, I’ve now upgraded our test machines all the way to gluster 4.1.4, but the symptoms are the same.
Post by Anoop C S
Post by Terry McGuire
[2018/09/12 09:37:17.873711, 0] ../source3/modules/vfs_glusterfs.c:996(vfs_gluster_stat)
glfs_stat(.) failed: Invalid argument
Might be related to https://bugzilla.samba.org/show_bug.cgi?id=13585.
Can you try installing a version of GlusterFS < 3.12.13 and see if it works normally?
This bug does seem to fit the symptoms, however my prod service is already < 3.12.3 and is not normal.

Perhaps my best option is to try downgrading samba to the original version and see if it restores proper function, until a patched version of Gluster is available. Or just live with slow FUSE-backed SMB for the time being.

Terry
Anoop C S
2018-09-18 10:44:30 UTC
Permalink
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated
to gluster 3.12.13, but the
symptoms
are the same.
Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?
If GlusterFS was at v3.10.12, are you sure that you were
experiencing issues with samba v4.7.1?
glusterfs 3.10.12
Version 4.7.1
Let me confirm one last time:
In your production environment, with GlusterFS v3.10.12 and Samba
v4.7.1, can you confirm whether issues are visible?

If so, do you see any issues for files/directories other than those
present directly under root of the share?

Also is it possible for you to check with `smbclient` utility from a
Linux machine to see whether issues are seen?
Post by Terry McGuire
As an experiment, I’ve now upgraded our test machines all the way to
gluster 4.1.4, but the symptoms are the same.
Yeah.. because the fix for upstream samba bug I mentioned in my last
reply is not yet available with any released version in 4.7.x series.
Thus updating GlusterFS will not get rid of that bug.
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
[2018/09/12 09:37:17.873711, 0]
../source3/modules/vfs_glusterfs.c:996(vfs_gluster_stat)
glfs_stat(.) failed: Invalid argument
Might be related to
https://bugzilla.samba.org/show_bug.cgi?id=13585.
Can you try installing a version of GlusterFS < 3.12.13 and see if it works normally?
This bug does seem to fit the symptoms, however my prod service is
already < 3.12.3 and is not normal.
I hope you meant < 3.12.13 this time :-)
Post by Terry McGuire
Perhaps my best option is to try downgrading samba to the original
version and see if it restores proper function, until a patched
version of Gluster is available.
As I explained above, issue was with Samba and fix has not yet made
into a release version. In short, following combinations should work
fine:

* samba version > 4.7.10 + any supported GlusterFS version
* samba version <= 4.7.10 + any supported GlusterFS version < 3.12.13
Post by Terry McGuire
Or just live with slow FUSE-backed SMB for the time being.
Let's track down the issue if there is one which is not yet identified.
Terry McGuire
2018-09-18 16:42:33 UTC
Permalink
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated
to gluster 3.12.13, but the
symptoms
are the same.
Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?
If GlusterFS was at v3.10.12, are you sure that you were
experiencing issues with samba v4.7.1?
glusterfs 3.10.12
Version 4.7.1
In your production environment, with GlusterFS v3.10.12 and Samba
v4.7.1, can you confirm whether issues are visible?
Can confirm. Issues visible with GlusterFS v3.10.12 and Samba v4.7.1.
Post by Anoop C S
If so, do you see any issues for files/directories other than those
present directly under root of the share?
Interesting! When I use Mac or Windows, I still see issues deeper in the hierarchy, but when I use Linux, I actually don’t see issues when I’m deeper in the hierarchy.
Post by Anoop C S
Also is it possible for you to check with `smbclient` utility from a
Linux machine to see whether issues are seen?
Yup, I see the same error as you mentioned in the bug report:

smb: \> mkdir test
NT_STATUS_INVALID_PARAMETER making remote directory \test
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Might be related to
https://bugzilla.samba.org/show_bug.cgi?id=13585 <https://bugzilla.samba.org/show_bug.cgi?id=13585>.
Can you try installing a version of GlusterFS < 3.12.13 and see if it works normally?
This bug does seem to fit the symptoms, however my prod service is
already < 3.12.3 and is not normal.
I hope you meant < 3.12.13 this time :-)
I did (but, pedantically-speaking, it is also < 3.12.3).
Post by Anoop C S
Post by Terry McGuire
Perhaps my best option is to try downgrading samba to the original
version and see if it restores proper function, until a patched
version of Gluster is available.
As I explained above, issue was with Samba and fix has not yet made
into a release version. In short, following combinations should work
* samba version > 4.7.10 + any supported GlusterFS version
* samba version <= 4.7.10 + any supported GlusterFS version < 3.12.13
Post by Terry McGuire
Or just live with slow FUSE-backed SMB for the time being.
Let's track down the issue if there is one which is not yet identified.
Okay. It does seem, considering the versions I’m running, that there’s something else (but similar) going on.

Terry
Anoop C S
2018-09-18 20:09:07 UTC
Permalink
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated
to gluster 3.12.13, but the
symptoms
are the same.
Did you mean 3.10.12 or 3.12.12?(your initial GlusterFS version)?
If GlusterFS was at v3.10.12, are you sure that you were
experiencing issues with samba v4.7.1?
glusterfs 3.10.12
Version 4.7.1
In your production environment, with GlusterFS v3.10.12 and Samba
v4.7.1, can you confirm whether issues are visible?
Can confirm. Issues visible with GlusterFS v3.10.12 and Samba v4.7.1.
Thanks for the confirmation.
Post by Terry McGuire
Post by Anoop C S
If so, do you see any issues for files/directories other than those
present directly under root of the share?
Interesting! When I use Mac or Windows, I still see issues deeper in the hierarchy, but when I
use Linux, I actually don’t see issues when I’m deeper in the hierarchy.
Any specific error dialogue window messages are displayed on Windows/Mac?
Post by Terry McGuire
Post by Anoop C S
Also is it possible for you to check with `smbclient` utility from a
Linux machine to see whether issues are seen?
smb: \> mkdir test
NT_STATUS_INVALID_PARAMETER making remote directory \test
Hm.. so you will need to have the samba fix for sure.
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Might be related to
https://bugzilla.samba.org/show_bug.cgi?id=13585.
Can you try installing a version of GlusterFS < 3.12.13 and see if
it works normally?
This bug does seem to fit the symptoms, however my prod service is
already < 3.12.3 and is not normal.
I hope you meant < 3.12.13 this time :-)
I did (but, pedantically-speaking, it is also < 3.12.3).
Got it.
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
Perhaps my best option is to try downgrading samba to the original
version and see if it restores proper function, until a patched
version of Gluster is available.
As I explained above, issue was with Samba and fix has not yet made
into a release version. In short, following combinations should work
* samba version > 4.7.10 + any supported GlusterFS version
* samba version <= 4.7.10 + any supported GlusterFS version < 3.12.13
Post by Terry McGuire
Or just live with slow FUSE-backed SMB for the time being.
Let's track down the issue if there is one which is not yet identified.
Okay. It does seem, considering the versions I’m running, that there’s something else (but
similar) going on.
Can you please share a fresh set of samba logs(preferably with higher debug level) and corresponding
glusterfs-<VOLNAME>-<IP>.log explaining the steps you tried to reproduce the issue?
Terry McGuire
2018-09-20 20:10:17 UTC
Permalink
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
If so, do you see any issues for files/directories other than those
present directly under root of the share?
Interesting! When I use Mac or Windows, I still see issues deeper in the hierarchy, but when I
use Linux, I actually don’t see issues when I’m deeper in the hierarchy.
Any specific error dialogue window messages are displayed on Windows/Mac?
On Mac: "The operation can’t be completed because an unexpected error occurred (error code -50).”
On Windows: "Z:\ is not accessible. The parameter is incorrect"
Post by Anoop C S
Can you please share a fresh set of samba logs(preferably with higher debug level) and corresponding
glusterfs-<VOLNAME>-<IP>.log explaining the steps you tried to reproduce the issue?
Ok, here’s a bunch of stuff. First, I put "log level = 3 passdb:2 auth:2” into smb.conf (in order to keep the log file a sane size). Then, to avoid complications with GUIs, I tested with smbclient on Ubuntu:
____________________
***@user-virtual-machine:~$ smbclient -U tmcguire -W STS '\\mfs-01.srv.ualberta.ca\module'
WARNING: The "syslog" option is deprecated
Enter tmcguire's password:
Domain=[STS] OS=[Windows 6.1] Server=[Samba 4.7.1]
smb: \> ls
. D 0 Thu Sep 20 10:19:05 2018
.. D 0 Wed Sep 5 15:58:07 2018
TerryCrap D 0 Tue Sep 18 09:54:53 2018
spinners D 0 Tue Jun 19 13:30:22 2018
testcrap D 0 Fri Mar 2 08:54:58 2018
stuff from ucast D 0 Mon Jul 30 11:05:03 2018

10737418240 blocks of size 1024. 9854798100 blocks available
smb: \> ls
NT_STATUS_INVALID_PARAMETER listing \*
smb: \> mkdir test
NT_STATUS_INVALID_PARAMETER making remote directory \test
smb: \> exit
***@user-virtual-machine:~$ smbclient -U tmcguire -W STS '\\mfs-01.srv.ualberta.ca\module'
WARNING: The "syslog" option is deprecated
Enter tmcguire's password:
Domain=[STS] OS=[Windows 6.1] Server=[Samba 4.7.1]
smb: \> ls
. D 0 Thu Sep 20 10:19:05 2018
.. D 0 Wed Sep 5 15:58:07 2018
TerryCrap D 0 Tue Sep 18 09:54:53 2018
spinners D 0 Tue Jun 19 13:30:22 2018
testcrap D 0 Fri Mar 2 08:54:58 2018
stuff from ucast D 0 Mon Jul 30 11:05:03 2018

10737418240 blocks of size 1024. 9854798100 blocks available
smb: \> ls
NT_STATUS_INVALID_PARAMETER listing \*
smb: \> mkdir test
NT_STATUS_INVALID_PARAMETER making remote directory \test
smb: \> cd spinners
smb: \spinners\> ls
. D 0 Tue Jun 19 13:30:22 2018
.. D 0 Thu Sep 20 10:19:05 2018
9820-motion.gif A 295879 Tue Jun 19 12:28:35 2018
fidget-spinner copy.png A 335089 Tue Jun 19 13:30:22 2018
fidget-spinner-centre copy.png A 57799 Tue Jun 19 13:07:45 2018
r_647810_4FeCH.gif A 3143085 Tue Jun 19 12:21:44 2018
source.gif A 989108 Fri May 25 08:07:35 2018
loading.gif A 8601 Fri May 25 08:07:08 2018
spinner.gif A 228462 Fri May 25 08:09:54 2018
fidget-spinner.png A 404752 Fri May 25 11:29:33 2018
fidget-spinner-centre.png A 44161 Fri May 25 11:30:01 2018
spinner-1.gif A 77029 Fri May 25 08:13:51 2018

10737418240 blocks of size 1024. 9854798100 blocks available
smb: \spinners\> mkdir test
smb: \spinners\> cd ../
smb: \> ls
NT_STATUS_INVALID_PARAMETER listing \*
smb: \> quit
___________________________

Interestingly, it seems that the first command I run on the share, even if it’s a write, works! Then, the following commands fail, unless I cd into a subdir.

The samba log still ended up pretty big, so I’ll include it at the end of this message.

I’m not quite sure what gluster log to include. There are several recently written logs with names similar to what you mention - like "localhost-mfs1-14453.log”, but they all have zero size. However, the glustershd.log is huge - 1GB+. There are many, many lines like this:

[2018-09-16 09:43:33.079561] W [MSGID: 114031] [client-rpc-fops.c:2928:client3_3_lookup_cbk] 0-mfs1-client-45: remote operation failed. Path: <gfid:9234c63b-5716-4e98-adc8-bf0f4e5db715> (9234c63b-5716-4e98-adc8-bf0f4e5db715) [No such file or directory]

Not sure if that’s related to this samba business or not. Anyway, here’s the samba log:

[2018/09/20 10:28:42.159957, 0] ../source3/modules/vfs_glusterfs.c:371(vfs_gluster_connect)
vfs_gluster_connect: mfs1: Initialized volume from servers localhost
[2018/09/20 10:32:21.093024, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 3 of length 112 (0 toread)
[2018/09/20 10:32:21.093089, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtconX (pid 14453) conn 0x0
[2018/09/20 10:32:21.093650, 3] ../lib/util/access.c:361(allow_access)
Allowed connection from 142.244.160.107 (142.244.160.107)
[2018/09/20 10:32:21.093744, 3] ../source3/smbd/service.c:595(make_connection_snum)
Connect path is '/tmp' for service [IPC$]
[2018/09/20 10:32:21.093802, 3] ../source3/smbd/vfs.c:113(vfs_init_default)
Initialising default vfs hooks
[2018/09/20 10:32:21.093837, 3] ../source3/smbd/vfs.c:139(vfs_init_custom)
Initialising custom vfs hooks from [/[Default VFS]/]
[2018/09/20 10:32:21.093954, 3] ../source3/smbd/service.c:841(make_connection_snum)
user-virtual-machine (ipv4:142.244.160.107:49890) connect to service IPC$ initially as user ***@sts.ad.ualberta.ca (uid=496619067, gid=496600513) (pid 14453)
[2018/09/20 10:32:21.094004, 3] ../source3/smbd/reply.c:1146(reply_tcon_and_X)
tconX service=IPC$
[2018/09/20 10:32:21.094784, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 4 of length 136 (0 toread)
[2018/09/20 10:32:21.094818, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:21.094918, 3] ../source3/smbd/msdfs.c:1008(get_referred_path)
get_referred_path: |module| in dfs path \mfs-01.srv.ualberta.ca\module is not a dfs root.
[2018/09/20 10:32:21.094952, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(9189) cmd=50 (SMBtrans2) NT_STATUS_NOT_FOUND
[2018/09/20 10:32:21.095674, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 5 of length 39 (0 toread)
[2018/09/20 10:32:21.095714, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtdis (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:21.095798, 3] ../source3/smbd/service.c:1120(close_cnum)
user-virtual-machine (ipv4:142.244.160.107:49890) closed connection to service IPC$
[2018/09/20 10:32:21.096452, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 6 of length 118 (0 toread)
[2018/09/20 10:32:21.096492, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtconX (pid 14453) conn 0x0
[2018/09/20 10:32:21.096561, 3] ../lib/util/access.c:361(allow_access)
Allowed connection from 142.244.160.107 (142.244.160.107)
[2018/09/20 10:32:21.096596, 3] ../libcli/security/dom_sid.c:210(dom_sid_parse_endp)
string_to_sid: SID @mfs-***@sts.ad.ualberta.ca is not in a valid format
[2018/09/20 10:32:21.098987, 3] ../source3/smbd/service.c:595(make_connection_snum)
Connect path is '/sa1' for service [module]
[2018/09/20 10:32:21.099022, 3] ../libcli/security/dom_sid.c:210(dom_sid_parse_endp)
string_to_sid: SID @mfs-***@sts.ad.ualberta.ca is not in a valid format
[2018/09/20 10:32:21.099257, 3] ../source3/smbd/vfs.c:113(vfs_init_default)
Initialising default vfs hooks
[2018/09/20 10:32:21.099283, 3] ../source3/smbd/vfs.c:139(vfs_init_custom)
Initialising custom vfs hooks from [/[Default VFS]/]
[2018/09/20 10:32:21.099301, 3] ../source3/smbd/vfs.c:139(vfs_init_custom)
Initialising custom vfs hooks from [glusterfs]
[2018/09/20 10:32:21.111540, 3] ../lib/util/modules.c:167(load_module_absolute_path)
load_module_absolute_path: Module '/usr/lib64/samba/vfs/glusterfs.so' loaded
[2018/09/20 10:32:25.530182, 0] ../source3/modules/vfs_glusterfs.c:371(vfs_gluster_connect)
vfs_gluster_connect: mfs1: Initialized volume from servers localhost
[2018/09/20 10:32:25.534609, 3] ../libcli/security/dom_sid.c:210(dom_sid_parse_endp)
string_to_sid: SID @mfs-***@sts.ad.ualberta.ca is not in a valid format
[2018/09/20 10:32:25.535273, 2] ../source3/smbd/service.c:841(make_connection_snum)
user-virtual-machine (ipv4:142.244.160.107:49890) connect to service module initially as user ***@sts.ad.ualberta.ca (uid=496619067, gid=496600513) (pid 14453)
[2018/09/20 10:32:25.535365, 3] ../source3/smbd/reply.c:1146(reply_tcon_and_X)
tconX service=MODULE
[2018/09/20 10:32:25.638379, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 7 of length 57 (0 toread)
[2018/09/20 10:32:25.638440, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:25.638492, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:26.704237, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 8 of length 92 (0 toread)
[2018/09/20 10:32:26.704312, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:26.706887, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:26.716541, 3] ../source3/smbd/dir.c:657(dptr_create)
creating new dirptr 256 for path ., expect_close = 1
[2018/09/20 10:32:26.716693, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found . fname=. (.)
[2018/09/20 10:32:26.716786, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found .. fname=.. (..)
[2018/09/20 10:32:26.727931, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found TerryCrap fname=TerryCrap (TerryCrap)
[2018/09/20 10:32:26.727994, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners fname=spinners (spinners)
[2018/09/20 10:32:26.728100, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found testcrap fname=testcrap (testcrap)
[2018/09/20 10:32:26.728129, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found stuff from ucast fname=stuff from ucast (stuff from ucast)
[2018/09/20 10:32:26.729341, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 9 of length 76 (0 toread)
[2018/09/20 10:32:26.729379, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:26.729408, 3] ../source3/smbd/trans2.c:4163(call_trans2qfsinfo)
call_trans2qfsinfo: level = 1007
[2018/09/20 10:32:26.729440, 3] ../source3/smbd/trans2.c:3456(smbd_do_qfsinfo)
smbd_do_qfsinfo: level = 1007
[2018/09/20 10:32:28.392715, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 10 of length 92 (0 toread)
[2018/09/20 10:32:28.392789, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:28.392826, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:28.400940, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for * (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:32:28.401000, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name * with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:28.401033, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(2750) cmd=50 (SMBtrans2) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:30.268945, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 11 of length 57 (0 toread)
[2018/09/20 10:32:30.269013, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:30.269085, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:32.112486, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 12 of length 52 (0 toread)
[2018/09/20 10:32:32.112557, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBmkdir (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:32.151298, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for test (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:32:32.151359, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name test with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:32.151388, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/reply.c(6181) cmd=0 (SMBmkdir) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:35.276117, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 13 of length 57 (0 toread)
[2018/09/20 10:32:35.276195, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:35.276261, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:40.428586, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 14 of length 57 (0 toread)
[2018/09/20 10:32:40.428656, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:40.428739, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:40.473429, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 15 of length 92 (0 toread)
[2018/09/20 10:32:40.473479, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:40.473551, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:40.479943, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for * (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:32:40.480007, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name * with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:40.480036, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(2750) cmd=50 (SMBtrans2) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:43.945195, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 16 of length 92 (0 toread)
[2018/09/20 10:32:43.945268, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:43.945304, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:43.951306, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for * (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:32:43.951343, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name * with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:43.951366, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(2750) cmd=50 (SMBtrans2) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:44.224757, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 17 of length 92 (0 toread)
[2018/09/20 10:32:44.224829, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:44.224865, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:44.229992, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for * (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:32:44.230029, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name * with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:44.230052, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(2750) cmd=50 (SMBtrans2) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:32:45.278472, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 18 of length 57 (0 toread)
[2018/09/20 10:32:45.278546, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:45.278644, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:45.953037, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 19 of length 100 (0 toread)
[2018/09/20 10:32:45.953110, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:45.953198, 3] ../source3/smbd/trans2.c:5814(call_trans2qfilepathinfo)
call_trans2qfilepathinfo: TRANSACT2_QPATHINFO: level = 257
[2018/09/20 10:32:45.956484, 3] ../source3/smbd/trans2.c:5976(call_trans2qfilepathinfo)
call_trans2qfilepathinfo spinners (fnum [fsp is NULL]) level=257 call=5 total_data=0
[2018/09/20 10:32:48.721081, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 20 of length 108 (0 toread)
[2018/09/20 10:32:48.721158, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:48.721196, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:32:48.747251, 3] ../source3/smbd/dir.c:657(dptr_create)
creating new dirptr 256 for path spinners, expect_close = 1
[2018/09/20 10:32:48.747370, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/. fname=. (.)
[2018/09/20 10:32:48.747469, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/.. fname=.. (..)
[2018/09/20 10:32:48.997250, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/9820-motion.gif fname=9820-motion.gif (9820-motion.gif)
[2018/09/20 10:32:48.997328, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/fidget-spinner copy.png fname=fidget-spinner copy.png (fidget-spinner copy.png)
[2018/09/20 10:32:48.997371, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/fidget-spinner-centre copy.png fname=fidget-spinner-centre copy.png (fidget-spinner-centre copy.png)
[2018/09/20 10:32:48.997408, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/r_647810_4FeCH.gif fname=r_647810_4FeCH.gif (r_647810_4FeCH.gif)
[2018/09/20 10:32:48.997446, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/source.gif fname=source.gif (source.gif)
[2018/09/20 10:32:48.997478, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/loading.gif fname=loading.gif (loading.gif)
[2018/09/20 10:32:48.997511, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/spinner.gif fname=spinner.gif (spinner.gif)
[2018/09/20 10:32:48.997582, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/fidget-spinner.png fname=fidget-spinner.png (fidget-spinner.png)
[2018/09/20 10:32:48.997616, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/fidget-spinner-centre.png fname=fidget-spinner-centre.png (fidget-spinner-centre.png)
[2018/09/20 10:32:48.997648, 3] ../source3/smbd/dir.c:1228(smbd_dirptr_get_entry)
smbd_dirptr_get_entry mask=[*] found spinners/spinner-1.gif fname=spinner-1.gif (spinner-1.gif)
[2018/09/20 10:32:48.999228, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 21 of length 76 (0 toread)
[2018/09/20 10:32:48.999273, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:48.999302, 3] ../source3/smbd/trans2.c:4163(call_trans2qfsinfo)
call_trans2qfsinfo: level = 1007
[2018/09/20 10:32:48.999332, 3] ../source3/smbd/trans2.c:3456(smbd_do_qfsinfo)
smbd_do_qfsinfo: level = 1007
[2018/09/20 10:32:50.343431, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 22 of length 57 (0 toread)
[2018/09/20 10:32:50.343502, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:50.343580, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:32:52.713115, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 23 of length 70 (0 toread)
[2018/09/20 10:32:52.713217, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBmkdir (pid 14453) conn 0x560316c737c0
[2018/09/20 10:32:52.966849, 3] ../source3/smbd/reply.c:6208(reply_mkdir)
mkdir spinners/test
[2018/09/20 10:32:55.284738, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 24 of length 57 (0 toread)
[2018/09/20 10:32:55.284805, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:32:55.284872, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:33:00.316833, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 25 of length 57 (0 toread)
[2018/09/20 10:33:00.316901, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:33:00.316958, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:33:02.672715, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 26 of length 92 (0 toread)
[2018/09/20 10:33:02.672785, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtrans2 (pid 14453) conn 0x560316c737c0
[2018/09/20 10:33:02.672861, 3] ../source3/smbd/trans2.c:2667(call_trans2findfirst)
call_trans2findfirst: dirtype = 16, maxentries = 1366, close_after_first=0, close_if_end = 1 requires_resume_key = 1 backup_priv = 0 level = 0x104, max_data_bytes = 65535
[2018/09/20 10:33:02.678985, 3] ../source3/smbd/vfs.c:1325(check_reduced_name)
check_reduce_name: couldn't get realpath for * (NT_STATUS_INVALID_PARAMETER)
[2018/09/20 10:33:02.679024, 3] ../source3/smbd/filename.c:1644(filename_convert_internal)
filename_convert_internal: check_name failed for name * with NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:33:02.679047, 3] ../source3/smbd/error.c:82(error_packet_set)
NT error packet at ../source3/smbd/trans2.c(2750) cmd=50 (SMBtrans2) NT_STATUS_INVALID_PARAMETER
[2018/09/20 10:33:05.298244, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 27 of length 57 (0 toread)
[2018/09/20 10:33:05.298315, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBecho (pid 14453) conn 0x0
[2018/09/20 10:33:05.298391, 3] ../source3/smbd/reply.c:5804(reply_echo)
echo 1 times
[2018/09/20 10:33:07.513168, 3] ../source3/smbd/process.c:1959(process_smb)
Transaction 28 of length 39 (0 toread)
[2018/09/20 10:33:07.513244, 3] ../source3/smbd/process.c:1539(switch_message)
switch message SMBtdis (pid 14453) conn 0x560316c737c0
[2018/09/20 10:33:07.513349, 2] ../source3/smbd/service.c:1120(close_cnum)
user-virtual-machine (ipv4:142.244.160.107:49890) closed connection to service module
[2018/09/20 10:33:16.129930, 3] ../source3/smbd/server_exit.c:248(exit_server_common)
Server exit (failed to receive smb request)
Anoop C S
2018-09-19 12:37:02 UTC
Permalink
Post by Terry McGuire
Post by Anoop C S
Can you please attach the output of `testparm -s` so as to look through how Samba is setup?
I have a setup where I could browse and work with a GlusterFS volume share made available to Windows
via vfs_glusterfs module on CentOS 7.5.1804 with glusterfs-3.10.12-1.el7 and samba-4.7.1-9.el7_5.

What am I missing? Are there any specific operation that leads to abnormal behaviours?
Post by Terry McGuire
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[share1]"
Processing section "[share2]"
Processing section "[nomodule]"
Processing section "[nomodule-nofruit]"
Processing section "[module]"
Processing section "[IPC$]"
WARNING: No path in service IPC$ - making it unavailable!
NOTE: Service IPC$ is flagged unavailable.
On an unrelated note:

I don't think your intention to make [IPC$] unavailable using the 'available' parameter would work
at all.
Post by Terry McGuire
Loaded services file OK.
idmap range not specified for domain '*'
ERROR: Invalid idmap range for domain *!
On an unrelated note:

Why haven't you specified range for default configuration? I think it is a must to set range for the
default configuration.
Post by Terry McGuire
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients
results in undefined behaviour.
Server role: ROLE_DOMAIN_MEMBER
# Global parameters
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 50
realm = XXXX.AD.UALBERTA.CA
security = ADS
workgroup = STS
glusterfs:volume = mfs1
idmap config * : backend = tdb
access based share enum = Yes
force create mode = 0777
force directory mode = 0777
include = /mfsmount/admin/etc/mfs/smb_shares.conf
kernel share modes = No
read only = No
smb encrypt = desired
vfs objects = glusterfs
[share1]
path = /share1
[share2]
path = /share2
Oh.. you are sharing sub-directories which is also fine.
Post by Terry McGuire
[nomodule]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects = fruit streams_xattr
Interesting..

Even this FUSE mounted GlusterFS share is not behaving normal? What errors do you see in glusterfs
fuse mount log(/var/log/glusterfs/mfsmount-.log) while accessing this share?
Post by Terry McGuire
[nomodule-nofruit]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects =
[module]
path = /share1
[IPC$]
available = No
vfs objects =
You may remove the whole [IPC$] section.
Post by Terry McGuire
Post by Anoop C S
Post by Terry McGuire
My gluster version initially was 3.10.12. I’ve since updated to gluster 3.12.13, but the
symptoms
are the same.
Does this sound familiar to anyone?
All mentioned symptoms point towards a disconnection. We need to find out the origin of this
disconnection. What do we have in logs under /var/log/samba/? Any errors?
[2018/09/12 09:37:17.873711, 0] ../source3/modules/vfs_glusterfs.c:996(vfs_gluster_stat)
glfs_stat(.) failed: Invalid argument
There appears to be some sort of connection remaining, as I can continue to cause these errors in
the server log by attempting I/O with the share.
This seems like the most promising lead to find the root cause. Hopefully you (or someone) can
interpret what it means, and what I might do about it (besides not using vfs_gluster anymore).
Regards,
Terry
Terry McGuire
2018-09-20 20:58:38 UTC
Permalink
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Can you please attach the output of `testparm -s` so as to look through how Samba is setup?
I have a setup where I could browse and work with a GlusterFS volume share made available to Windows
via vfs_glusterfs module on CentOS 7.5.1804 with glusterfs-3.10.12-1.el7 and samba-4.7.1-9.el7_5.
What am I missing? Are there any specific operation that leads to abnormal behaviours?
It seems that, when using smbclient to keep things simple, the first command in the share’s root works, even if it’s a write. The following commands, even if it’s just an ls, fails.

One difference that might be making the difference is that my gluster volume is distributed-dispersed. This seems also to break the vfs_fruit module.
Post by Anoop C S
Post by Terry McGuire
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[share1]"
Processing section "[share2]"
Processing section "[nomodule]"
Processing section "[nomodule-nofruit]"
Processing section "[module]"
Processing section "[IPC$]"
WARNING: No path in service IPC$ - making it unavailable!
NOTE: Service IPC$ is flagged unavailable.
I don't think your intention to make [IPC$] unavailable using the 'available' parameter would work
at all.
I assume this IPC$ stuff is just an artifact of how I built my smb.conf file. I put "vfs objects = glusterfs” into the global stanza, so it didn’t need to be added to each share stanza, but I discovered that this broke IPC$ in such a way as to make no share accessible. To fix this, I added a share stanza for IPC$ that includes only “vfs objects =". Maybe that’s dumb, but it worked, and, I guess, results in what we see here.
Post by Anoop C S
Post by Terry McGuire
Loaded services file OK.
idmap range not specified for domain '*'
ERROR: Invalid idmap range for domain *!
Why haven't you specified range for default configuration? I think it is a must to set range for the
default configuration.
I guess because I’m clueless enough not to know that I should. We’re authenticating samba users from Windows Active Directory, and I’m really clueless about that. We got things to the point that they were working, and called it a day.
Post by Anoop C S
Post by Terry McGuire
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X clients
results in undefined behaviour.
Server role: ROLE_DOMAIN_MEMBER
# Global parameters
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 50
realm = XXXX.AD.UALBERTA.CA
security = ADS
workgroup = STS
glusterfs:volume = mfs1
idmap config * : backend = tdb
access based share enum = Yes
force create mode = 0777
force directory mode = 0777
include = /mfsmount/admin/etc/mfs/smb_shares.conf
kernel share modes = No
read only = No
smb encrypt = desired
vfs objects = glusterfs
[share1]
path = /share1
[share2]
path = /share2
Oh.. you are sharing sub-directories which is also fine.
We *only* share subdirs of the gluster volume, never the volume itself.
Post by Anoop C S
Post by Terry McGuire
[nomodule]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects = fruit streams_xattr
Interesting..
Even this FUSE mounted GlusterFS share is not behaving normal? What errors do you see in glusterfs
fuse mount log(/var/log/glusterfs/mfsmount-.log) while accessing this share?
This one isn’t affected by the current samba issue, but it’s affected by another issue. (I actually posted about it a while ago - subject “vfs_fruit and extended attributes”- and I think you responded, but it didn’t go anywhere.) We discovered that the vfs_fruit module seems to interact poorly with our distributed-dispersed gluster volume. To learn this, we made a test replicated volume and it worked fine.

Ironically, we decided we could live without vfs_fruit when we discovered vfs_glusterfs. Now we have neither. :-(
Post by Anoop C S
Post by Terry McGuire
[nomodule-nofruit]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects =
[module]
path = /share1
[IPC$]
available = No
vfs objects =
You may remove the whole [IPC$] section.
IPC$ stuff explained above.

Terry
Anoop C S
2018-09-21 11:18:03 UTC
Permalink
Post by Anoop C S
Post by Terry McGuire
Post by Anoop C S
Can you please attach the output of `testparm -s` so as to look through how Samba is setup?
I have a setup where I could browse and work with a GlusterFS volume share made available to
Windows
via vfs_glusterfs module on CentOS 7.5.1804 with glusterfs-3.10.12-1.el7 and samba-4.7.1-
9.el7_5.
What am I missing? Are there any specific operation that leads to abnormal behaviours?
It seems that, when using smbclient to keep things simple, the first command in the share’s root
works, even if it’s a write. The following commands, even if it’s just an ls, fails.
One difference that might be making the difference is that my gluster volume is distributed-
dispersed. This seems also to break the vfs_fruit module.
Post by Anoop C S
Post by Terry McGuire
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[share1]"
Processing section "[share2]"
Processing section "[nomodule]"
Processing section "[nomodule-nofruit]"
Processing section "[module]"
Processing section "[IPC$]"
WARNING: No path in service IPC$ - making it unavailable!
NOTE: Service IPC$ is flagged unavailable.
I don't think your intention to make [IPC$] unavailable using the 'available' parameter would
work
at all.
I assume this IPC$ stuff is just an artifact of how I built my smb.conf file. I put "vfs objects
= glusterfs” into the global stanza, so it didn’t need to be added to each share stanza, but
I discovered that this broke IPC$ in such a way as to make no share accessible. To fix this, I
added a share stanza for IPC$ that includes only “vfs objects =". Maybe that’s dumb, but it
worked, and, I guess, results in what we see here.
Ok. First things first. Better move "vfs objects" parameter from [global] section to those share
sections where it is required. This will help you avoid problems in future when you add non-
glusterfs shares(and you forget adding empty "vfs objects" line).
Post by Anoop C S
Post by Terry McGuire
Loaded services file OK.
idmap range not specified for domain '*'
ERROR: Invalid idmap range for domain *!
Why haven't you specified range for default configuration? I think it is a must to set range for
the
default configuration.
I guess because I’m clueless enough not to know that I should. We’re authenticating samba users
from Windows Active Directory, and I’m really clueless about that. We got things to the point
that they were working, and called it a day.
Hm.. we will take that up later.
Post by Anoop C S
Post by Terry McGuire
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
WARNING: some services use vfs_fruit, others don't. Mounting them in conjunction on OS X
clients
results in undefined behaviour.
Server role: ROLE_DOMAIN_MEMBER
# Global parameters
[global]
log file = /var/log/samba/log.%m
map to guest = Bad User
max log size = 50
realm = XXXX.AD.UALBERTA.CA
security = ADS
workgroup = STS
glusterfs:volume = mfs1
idmap config * : backend = tdb
access based share enum = Yes
force create mode = 0777
force directory mode = 0777
include = /mfsmount/admin/etc/mfs/smb_shares.conf
kernel share modes = No
read only = No
smb encrypt = desired
vfs objects = glusterfs
[share1]
path = /share1
[share2]
path = /share2
Oh.. you are sharing sub-directories which is also fine.
We *only* share subdirs of the gluster volume, never the volume itself.
Post by Anoop C S
Post by Terry McGuire
[nomodule]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects = fruit streams_xattr
Interesting..
Even this FUSE mounted GlusterFS share is not behaving normal? What errors do you see in
glusterfs
fuse mount log(/var/log/glusterfs/mfsmount-.log) while accessing this share?
This one isn’t affected by the current samba issue, but it’s affected by another issue. (I
actually posted about it a while ago - subject “vfs_fruit and extended attributes”- and I think
you responded, but it didn’t go anywhere.) We discovered that the vfs_fruit module seems to
interact poorly with our distributed-dispersed gluster volume. To learn this, we made a test
replicated volume and it worked fine.
We can look into issue with vfs_fruit + FUSE mount + disperse volume(interesting though..) after we
finish debugging the current problem.
Ironically, we decided we could live without vfs_fruit when we discovered vfs_glusterfs. Now we
have neither. :-(
Post by Anoop C S
Post by Terry McGuire
[nomodule-nofruit]
kernel share modes = Yes
path = /mfsmount/share1
vfs objects =
[module]
path = /share1
[IPC$]
available = No
vfs objects =
You may remove the whole [IPC$] section.
IPC$ stuff explained above.
Base on your explanation I would repeat my previous request to remove [IPC$] and follow what I
suggested above on moving "vfs objects" to individual shares.

Isn't shares [share1] and [module] same?
Terry McGuire
2018-09-24 16:16:02 UTC
Permalink
Post by Anoop C S
Base on your explanation I would repeat my previous request to remove [IPC$] and follow what I
suggested above on moving "vfs objects" to individual shares.
Ok, I’ve now rearranged my smb.conf files on our test system to prevent the IPC$ issue, and I’ve removed the IPC$ stanza. testparm -s no longer warns about IPC$ stuff, but it still complains about idmap range. There’s no difference in behaviour regarding vfs_gluster issue.
Post by Anoop C S
Isn't shares [share1] and [module] same?
It is. I created new shares of the same directory, with obvious names, to explore different configs as I diagnosed the issue.

Terry

Loading...