From the quoted config file, i would assume that this is a Samba version that has been installed from another source.
 
I have not seen this exact problem. If it can be recreated, then it might be useful to collect a trace and contact the supplier of the installed Samba for support.
 
Note that Spectrum Scale since 4.1.1 includes protocols support which includes Samba. If that is used, then any problems with the Spectrum Scale provided Samba can be addressed through Spectrum Scale support. (As a sidenote to the noted problem, SMB2 leases are currently not supported with Samba in Spectrum Scale).
 
Regards,

Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ
[email protected]  ||  +1-520-799-2469    (T/L: 321-2469)
 
 
----- Original message -----
From: Bart Van Damme <[email protected]>
Sent by: [email protected]
To: [email protected]
Cc:
Subject: [gpfsug-discuss] SMB2 leases - oplocks - growing files
Date: Fri, Sep 1, 2017 2:31 AM
 
We are a company located in Belgium that mainly implements spectrum scale clusters in the Media and broadcasting industry. 
 
Currently we have a customer who wants to export the scale file system over samba 4.5 and 4.6.  
In these versions the SMB2 leases are activated by default for enhancing the oplocks system.
 
The problem is when this option is not disabled Adobe (and probably Windows) is not notified the size of the file have changed, resulting that reading growing file in Adobe is not working, the timeline is not updated.
 
Does anybody had this issues before and know how to solve it.
 
 
 
This is the smb.conf file:
 
 
============================

# Global options

smb2 leases = yes

client use spnego = yes

clustering = yes

unix extensions = no

mangled names = no

ea support = yes

store dos attributes = yes

map readonly = no

map archive = yes

map system = no

force unknown acl user = yes

obey pam restrictions = no

deadtime = 480

disable netbios = yes

server signing = disabled

server min protocol = SMB2

smb encrypt = off

 

# We do not allow guest usage.

guest ok = no

guest account = nobody

map to guest = bad user

 

# disable printing

load printers = no

printing = bsd

printcap name = /dev/null

disable spoolss = yes

 

# log settings

log file = /var/log/samba/log.%m

# max 500KB per log file, then rotate

max log size = 500

log level = 1 passdb:1 auth:1 winbind:1  idmap:1

 

#============ Share Definitions ============

[pfs]

comment = GPFS

path = /gpfs/pfs

valid users = @ug_numpr

writeable = yes

inherit permissions = yes

create mask = 664

force create mode = 664

nfs4:chown = yes

nfs4:acedup = merge

nfs4:mode = special

fileid:algorithm = fsname

vfs objects = shadow_copy2 gpfs fileid full_audit

full_audit:prefix = %u|%I|%m|%S

full_audit:success = rename unlink rmdir

full_audit:failure = none

full_audit:facility = local6

full_audit:priority = NOTICE

shadow:fixinodes = yes

gpfs:sharemodes = yes

gpfs:winattr = yes

gpfs:leases = no

locking = yes

posix locking = yes

oplocks = yes

kernel oplocks = no

 
 
Grtz,
 
Bart
 
 
 
 
Bart Van Damme
Customer Project Manager
SDNsquare
Technologiepark 3,
9052 Zwijnaarde, Belgium
 
 

 

 

 

This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify the sender immediately and delete this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can be accepted for any loss or damage arising from its receipt or subsequent use of this email.
 
Virusvrij. www.avast.com
 

_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

Reply via email to