From owner-freebsd-current@freebsd.org Fri May 6 17:15:41 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 A206EB2FCEC for ; Fri, 6 May 2016 17:15:41 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 356581FA3 for ; Fri, 6 May 2016 17:15:41 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wm0-x241.google.com with SMTP id w143so9772515wmw.3 for ; Fri, 06 May 2016 10:15:41 -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=JjYo6qC93wHv2iCk/HBWiwyyNncqE2iJ/LZTaWpk9sQ=; b=pmIOKX9GZXfw32UgExUFrGG3xrYRATuC05FNo3tGrX4YOhd3C+ZEcVa0CzmakSdEHI 5DQsH2yHV+gGQx7wApbEz76w9wBip6GtskqaHoNWe6sJ6gGirRBgqsb/kAop+z8ncCfc xLKtoZjs8ivm3ha1o8SYzfYHdd9bYlVHjFRYoBxdUUzx7FtRWUgMUTyL6d6OlyRXW7yn FVBheiXEfYwHpjuatScdnuDJo2kEvu6JcjEFR+DZEqQzvTZ5L6Dyd34EYfsoTFIPnQZt Fht1D7yeTBC0OQxCpGboOhW7QpbuZUBoTfPetjywZH+YZOnx/T2cQq2U58l7cCNWr0Ns JhbQ== 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=JjYo6qC93wHv2iCk/HBWiwyyNncqE2iJ/LZTaWpk9sQ=; b=O3xHPJIFNQovlGaGHdViQOUd0IPHEEBYqes66NE4WGfSNk7LV88QHA5B8red4PEJQo QTppuRHsd9gS9+hVDNU3Q1npqvMDHbftvZ+KvmwpMRoYJjUuzhPb/eoJHWxBzgoT+drT 0kYNXjOOhL1iIoxJCVI4UxjSPNaL3CGt5ZEmrBf+kvew69yCtL7EkaE4nC3JY3paM8xA kFLNoNeSKdkMZK0Z2l/5XlvOyeAnb8mBsK4Qux1p/chKTJwl5c3sUD9axYHgXC/bu8mO iFvin8kQW0myREBthMFuV0Crz46emwd6NCyJquO+d5HahzcomlxrhwORwc0YctaGXKKV tIUw== X-Gm-Message-State: AOPr4FUc4tF8IlyYOpwjkb9kXr6FPq4yfnqT7wKQdXMDrNGHNbPTFoBM4qHWtl8lQkrfvg== X-Received: by 10.194.20.162 with SMTP id o2mr20948534wje.78.1462554939727; Fri, 06 May 2016 10:15:39 -0700 (PDT) Received: from brick (eun204.neoplus.adsl.tpnet.pl. [83.20.185.204]) by smtp.gmail.com with ESMTPSA id he10sm7293135wjc.21.2016.05.06.10.15.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 May 2016 10:15:38 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Fri, 6 May 2016 19:15:35 +0200 From: Edward Tomasz Napiera?a To: "O. Hartmann" Cc: FreeBSD CURRENT Subject: Re: r298143: something wrong with autofs? Message-ID: <20160506171535.GA4357@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> <20160504184151.GA12165@brick> <20160506140815.4974bf83.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: <20160506140815.4974bf83.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: Fri, 06 May 2016 17:15:41 -0000 On 0506T1408, O. Hartmann wrote: > Am Wed, 4 May 2016 20:41:51 +0200 > Edward Tomasz Napiera?a schrieb: > > > 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! > > Hello Edward, > > sorry for the late answer. I can not (I'm not allowed!) offer config data from any of the > lab's/bureaus computers, so I decided to check again the whole config, since several > boxes do as expected and others not (which is the weird part). I found a simple culprit: > somewhere in the near past, /etc/auto_master received an update and I simply have > overwritten the old one with the new one. So the autofs system never checked the exported > filessystem's list given by a mandatory /etc/auto_ext file and in the logical consequence, > no filesystem defined there was mounted. > > After simply adding the missing line the mounting of the expected filesystems worked > again. Huh, that explains. IIRC some time (few weeks?) ago there was a problem in 11-CURRENT that made "make installworld" overwrite some of the config files, as if there were binaries. Looks like you got bitten by this. Let me know if you find anything else with autofs that looks suspicious. Thanks :-)