From owner-freebsd-current@freebsd.org Wed May 4 18:41:58 2016 Return-Path: Delivered-To: freebsd-current@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 45F45B2DB1D for ; Wed, 4 May 2016 18:41:58 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D912F1680 for ; Wed, 4 May 2016 18:41:57 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id e201so199813193wme.0 for ; Wed, 04 May 2016 11:41:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=/vpExOT4WjXgM1/IUtoUJTk1FKlG3hvXiyVHcWWYYd4=; b=b9vmryWA8QBNf+rawofgRTtji24+ujLVecegSM+e805o6jdkpbKUJSq+rO1kxvfolQ mWvatI/miXQejoKBf2EFN4detDqysyxqPeoP45iSnRhAU476m+mTh7Rd/Po81QpMoWfq LPM9Nvt5sh2d6+SgrMB1LzQHmH4rnXM9OSFsbEcTJFpkd3dQ7oodduu9uBQ1pW+tQu3g rRE/W5J6SpQJArOAMC4ALmnE5E7FmfOWXIaYe/ccL5N6uLNgyrmFGSbpDNq4yxJfRD0E mxlq3jOLvnxmHCY+RkX/5mXWBf0LHGH2cmDYrk9dRr4JA0MgX5PMcRRa1Ng6sDvfbf7E JKvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=/vpExOT4WjXgM1/IUtoUJTk1FKlG3hvXiyVHcWWYYd4=; b=mfQXQ0WmoD9QvOlJr6Xr6sOclt+ZefMq4LQBQuzt2X+JScpB8BtxI0lR4jg0nWy/Dt pddeJHvZ/iiEvQyxCpJ/sRrLPQDiFWFoL+pukAKXRVMh/Ujzo3VG9t0VAUoO9Ko70Oai riZxFh5UnGSEGb0okUZTir1tPoUMhbTWjHGX5VYEW7xkKGlIat0QYl0QiB6X127HK9Yj pBdDP5aY3vCAa+X3X1iuiFP9mpAiYhF1n4ni+bU98BnAMy0n9nqzevy8oex7BofwMXZy iTl2ADUX40NQ1+h4MlrFWQSQx2nDjD+5bAo9c2BGw75i3kV0X+6a88Mx0q+QK9+3AzkU boiA== X-Gm-Message-State: AOPr4FU7JIFqx2Zr7p34UfxHo1RPN6UCTmCzR5/av57gKEV5GZOhWBvlIZ5hal1RIVWB5w== X-Received: by 10.28.22.134 with SMTP id 128mr10473326wmw.16.1462387315764; Wed, 04 May 2016 11:41:55 -0700 (PDT) Received: from brick (aif55.neoplus.adsl.tpnet.pl. [83.25.213.55]) by smtp.gmail.com with ESMTPSA id gr4sm5655277wjd.23.2016.05.04.11.41.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 May 2016 11:41:55 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Wed, 4 May 2016 20:41:51 +0200 From: Edward Tomasz Napiera?a To: "O. Hartmann" Cc: FreeBSD CURRENT Subject: Re: r298143: something wrong with autofs? Message-ID: <20160504184151.GA12165@brick> Mail-Followup-To: "O. Hartmann" , FreeBSD CURRENT References: <20160417105741.170f6f14.ohartman@zedat.fu-berlin.de> <20160417103944.GA30972@brick.home> <20160503184950.15e58c87.ohartman@zedat.fu-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160503184950.15e58c87.ohartman@zedat.fu-berlin.de> User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2016 18:41:58 -0000 On 0503T1849, O. Hartmann wrote: > Am Sun, 17 Apr 2016 12:39:44 +0200 > Edward Tomasz Napierała schrieb: > > > On 0417T1057, O. Hartmann wrote: > > > > > > Running FreeBSD 11.0-CURRENT #32 r298143: Sun Apr 17 09:48:26 CEST 2016 amd64, on > > > both server and client, reveals today that AUTOFS seems not to work. Did something > > > changed unnoticed? > > > > > > I realized, that no exported filesystem is bound so far. On the server's side, all > > > > "Bound"? > > ... means: the cleint does not mount/bind the NFS exported filesystem anymore. Ok. > > > daemons necessary are configured as they were before in a working state and as I can > > > see so far, they are up and running and also listening to their sockets/IPs. > > > > Could you describe in more detail what are you seeing? Also, the usual autofs > > debugging technique ("pkill automountd && while :; do automountd -d; done") might > > sched some light. > > Well, I see nothing! That is my problem. I setup several NFSv4 exported filesystems which > were mounted on demand via autofs - that workd. Since I do not use/need those filesystems > on a dailt basis, I realized too late that in the meanwhile those filesystems are not > present on the client (autofs) anymore. I'm not aware of having changed anything in the > configuration and I didn't receive any heads-ups that essential changes had been made. Hm, it certainly seems weird. Are the autofs instances mounted where there should be? Could you send me your /etc/auto_master, the maps, and dmesg output? Thanks!