From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 88A4AC43381 for ; Fri, 22 Feb 2019 17:16:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 58E3B20675 for ; Fri, 22 Feb 2019 17:16:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725832AbfBVRQm (ORCPT ); Fri, 22 Feb 2019 12:16:42 -0500 Received: from smtp03.citrix.com ([162.221.156.55]:29334 "EHLO SMTP03.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726019AbfBVRQl (ORCPT ); Fri, 22 Feb 2019 12:16:41 -0500 X-IronPort-AV: E=Sophos;i="5.58,400,1544486400"; d="scan'208";a="78844600" Subject: Re: Failure to reconnect after cluster failvoer To: Tom Talpey , Steve French CC: CIFS References: <70e91b0b-4bca-60ea-19cf-3df0f49d4e5a@citrix.com> From: Ross Lagerwall Message-ID: <07c8e090-afed-6219-7d24-addfa660d8dd@citrix.com> Date: Fri, 22 Feb 2019 17:16:38 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-cifs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-cifs@vger.kernel.org On 2/21/19 5:59 PM, Tom Talpey wrote: > The reconnect is apparently using a dotted-quad as the servername, and you can see the auth is forced to NTLM as a consequence. Is that the way you initially mounted the share (i.e. mount 10.71.217.50:/smbshare /mnt)? > > -----Original Message----- > From: linux-cifs-owner@vger.kernel.org On Behalf Of Steve French > Sent: Thursday, February 21, 2019 9:07 AM > To: Ross Lagerwall > Cc: CIFS > Subject: Re: Failure to reconnect after cluster failvoer > > Couple quick thoughts. > > Does this work on current kernels (5.0 for example). > > Was thinking about patches that might affect this like: > - "cifs: connect to servername instead of IP for IPC$ share" > - "smb3: on reconnect set PreviousSessionId field" > - Paulo's patches (has cifs-utils coreq) to reconnect to new IP > address if hostname's IP address changed and his add support for > failover > - Paulo's patch to remove trailing slashes from server UNC name > I've reproduced this with 5.0-rc7 and the latest cifs-utils from git. The share was mounted as follows (yes, by IP): mount.cifs -o vers=3.0,cache=loose,actimeo=0,username=x,domain=y,password=z '//10.71.217.31/smbshare' /mnt Here is the tcpdump when it fails to reconnect properly: http://s000.tinyupload.com/index.php?file_id=55518118986864684971 The initial connection is at timestamp 0s, reconnection at 13s, STATUS_NETWORK_NAME_DELETED at 60s. For comparison, here is a tcpdump using the "fix" from my previous mail: http://s000.tinyupload.com/index.php?file_id=04243963024741599425 The initial connection is at timestamp 0s, reconnection at 34s, successful read request at 215s. Note that the tree connect for IPC$ only happens _after_ the tree connect for the share succeeds. Thanks, -- Ross Lagerwall