From owner-freebsd-net@freebsd.org Tue Oct 29 02:53:05 2019 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C4B2166D62 for ; Tue, 29 Oct 2019 02:53:05 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta01.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 472GNc4SMpz3LyB for ; Tue, 29 Oct 2019 02:53:04 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.177.163]) by cmsmtp with ESMTP id PHcyiyKNp7K91PHd0iXiCb; Tue, 29 Oct 2019 02:53:03 +0000 Date: Tue, 29 Oct 2019 02:52:57 +0000 From: "Thomas Mueller" To: freebsd-net@freebsd.org Subject: Umounting an NFS-mounted share after connection is lost? X-CMAE-Envelope: MS4wfNX8L166COf4uxfh2ChZs3li1aFTvZMRy9kqO7TfZQWEDPmslKotBiNs3dLwXw6ouIKueINymbkTsjWb7Ig5BMW8U7b1xkLR0xMSXsjDFManaDz339IX 3YTJPOrB4mE4yjHouNE8m+8q8NhC8wEn+k2fEZc2p72TwLQU0EtiATo5 X-Rspamd-Queue-Id: 472GNc4SMpz3LyB X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of mueller6722@twc.com designates 107.14.73.226 as permitted sender) smtp.mailfrom=mueller6722@twc.com X-Spamd-Result: default: False [1.26 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.982,0]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.14.73.0/24]; FREEMAIL_FROM(0.00)[twc.com]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; TO_DN_NONE(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.96)[-0.959,0]; MISSING_MID(2.50)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.00)[ip: (-5.24), ipnet: 107.14.73.0/24(-2.67), asn: 7843(-2.13), country: US(-0.05)]; RCVD_IN_DNSWL_NONE(0.00)[226.73.14.107.list.dnswl.org : 127.0.5.0]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[twc.com]; RECEIVED_SPAMHAUS_PBL(0.00)[163.177.28.96.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; RWL_MAILSPIKE_POSSIBLE(0.00)[226.73.14.107.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7843, ipnet:107.14.73.0/24, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[twc.com]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Oct 2019 02:53:05 -0000 How do you umount a file system that has been mounted with mount_nfs when the connection is lost? Server can crash, cable modem could quit and not hold power, or a change in cable modem or router could change 192.168.0.1 to 192.168.1.1 . Running umount hangs the terminal session. Is there a way out short of rebooting? In the case of a server crash, I could reboot the server, mount the desired partition, run "/etc/rc.d/mountd restart", and be good again. But last weekend, the cable modem-router lost power, could be restored by unplugging and replugging, but would only hold for maybe a half minute before going dark again. Charter Spectrum support told me that I could get a free replacement, which I did, cable modem and router were two separate pieces this time. I was able to install the equipment successfully but noticed that the router address was 192.168.1.1 rather than the old 192.168.0.1 . I was left with /homeawayfromhome that I couldn't unmount except by rebooting. Tom