From owner-freebsd-net@freebsd.org Fri Jan 13 23:47:49 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50DEBCAE90B for ; Fri, 13 Jan 2017 23:47:49 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: from h2.pinyon.org (h2.pinyon.org [65.101.20.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DFB31A6D for ; Fri, 13 Jan 2017 23:47:48 +0000 (UTC) (envelope-from rcarter@pinyon.org) Received: by h2.pinyon.org (Postfix, from userid 58) id 862DE128FE; Fri, 13 Jan 2017 16:47:42 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1484351262; bh=+tXSYfqCWp8DN+GAlOvAzgvUXSRdfiXVj7fT17axNoU=; h=Subject:To:References:From:Date:In-Reply-To; b=dfGb6wR2hLmq5Ur8z5knmudN/bbD6xSxtHAhqPc3xsVZA3qxxRv25zx/v7ujFZ0b/ mZkc9KJ1W+1tRg8QzIfd+zi1K9vZeMNyjo2Pfp5zeastkoYwC+7a1tRw4pBzT/lUgh U1v/POVxrqEAhorIKQm9LnJFmbgA1nHnVBrrgr74= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on h2.pinyon.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from [10.0.10.15] (h1.pinyon.org [65.101.20.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by h2.pinyon.org (Postfix) with ESMTPSA id AFB77128EF for ; Fri, 13 Jan 2017 16:47:41 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pinyon.org; s=DKIM; t=1484351261; bh=+tXSYfqCWp8DN+GAlOvAzgvUXSRdfiXVj7fT17axNoU=; h=Subject:To:References:From:Date:In-Reply-To; b=lb4Amf46c1rrDRE6X/0foKzNpNcnSf/g6PXCV/tF4mpkHqD0QvOZHJa2BLE/0Lk7c lGo4PBx2ktEKgojVmQshj5QTJahTC3zJx+hc6pj5J076L+5UMtb8mlokZGhSI9OUhG eeAYVeQ971d+zld0qV8IfUb6+waoD+wg0UuRyoO4= Subject: Re: NFSv4 stuck To: freebsd-net@freebsd.org References: <20170111220818.GD30374@zxy.spb.ru> <20170111225922.GE30374@zxy.spb.ru> <20170111235020.GF30374@zxy.spb.ru> <58771EA6.1020104@grosbein.net> <20170112131504.GG30374@zxy.spb.ru> From: "Russell L. Carter" Message-ID: <44a7df9c-b1a3-1191-05af-d73235bdf15a@pinyon.org> Date: Fri, 13 Jan 2017 16:47:41 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 23:47:49 -0000 On 01/12/17 16:08, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > >> On Thu, Jan 12, 2017 at 01:13:58PM +0700, Eugene Grosbein wrote: >> >>> 12.01.2017 6:50, Slawa Olhovchenkov пишет: >>>> On Wed, Jan 11, 2017 at 03:20:22PM -0800, Michael Sinatra wrote: >>>> >>>>> On 01/11/17 14:59, Slawa Olhovchenkov wrote: >>>>>> On Wed, Jan 11, 2017 at 10:39:42PM +0000, Rick Macklem wrote: >>>>>> >>>>>>> "umount -f" is your only chance. However, if there is already a non-forced >>>>>>> dismount stuck, it won't work because the non-forced dismount will have >>>>>>> the mounted-on vnode locked. >>>>>> >>>>>> I am use 'intr,soft' flags -- why ignored? >>>>> >>>>> intr and soft are considered dangerous with nfsv4. See the "BUGS" >>>>> section of the mount_nfs(8) man page. >>>> >>>> Currently I am see dangerous w/o intr: system need reboot, application >>>> don't killable. >>> >>> NFSv4 confiders "intr,soft" dangerous for data generated by poorly written applications, not for a OS. >> >> What data? In may case no data. > Certain NFSv4 operations (such as open and byte range locking) are strictly ordered using a > seqid#. If you fail an RPC in progress (via a soft timeout or intr via a signal) then this seqid gets > out of sync between client and server and your mount is badly broken. > > I do not believe this caused your hang though, since processes were sleeping on rpccon, which > means they were trying to do a new TCP connection to the server unsuccessfully. > - Which normally indicates a problem with your underlying network fabric. > stuff snipped... FWIW I see this hang too, requiring a hard reset of the power to get the server to reboot. I learned the hard way about umount -f. Modestly annoying when you reboot the package server and then forget to umount -f && mount package server, and *then* do 'pkg install some-package' My linux clients don't have this problem. This is on 11/stable Russell > rick > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >