[gpfsug-discuss] Samba via CES

[Christof Schmitt]

The client has to reconnect, open the file again and reissue request that 
have not been completed. Without persistent handles, the main risk is that 
another client can step in and access the same file in the meantime. With 
persistent handles, access from other clients would be prevented for a 
defined amount of time.

Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ
christof.schmitt at us.ibm.com  ||  +1-520-799-2469    (T/L: 321-2469)



From:   Lukas Hejtmanek <xhejtman at ics.muni.cz>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   09/27/2016 02:43 PM
Subject:        Re: [gpfsug-discuss] Samba via CES
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



On Tue, Sep 27, 2016 at 02:36:37PM -0700, Christof Schmitt wrote:
> When a CES node fails, protocol clients have to reconnect to one of the 
> remaining nodes.
> 
> Samba in CES does not support persistent handles. This is indicated in 
the 
> documentation:
> 
> 
http://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.1/com.ibm.spectrum.scale.v4r21.doc/bl1adm_smbexportlimits.htm#bl1adm_smbexportlimits

> 
> "Only mandatory SMB3 protocol features are supported. "

well, but in this case, HA feature is a bit pointless as node fail results 
in
a client failure as well as reconnect does not seem to be automatic if 
there is
on going traffic.. more precisely reconnect is automatic but without
persistent handles, the client receives write protect error immediately. 

-- 
Lukáš Hejtmánek
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss