From owner-freebsd-net@freebsd.org Thu Aug 30 14:08:11 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B25E5109F6A0 for ; Thu, 30 Aug 2018 14:08:11 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f172.google.com (mail-lj1-f172.google.com [209.85.208.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 36AE481FB6 for ; Thu, 30 Aug 2018 14:08:11 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f172.google.com with SMTP id u83-v6so7355171lje.12 for ; Thu, 30 Aug 2018 07:08:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4fhpUrnUGLLL9cZ/r/4ZPhLC/EZEE/ebIgi5r4Kai2s=; b=cDL83B8cJ4uMa0WCVe+2ITew5WUMhzcYNXnbYiV7vR/2PKTPm1JaxZsH6LrbpuUfqZ /5+rkMJb8vQJmIjcuGuHKR3hXNLQ+KJIgeQh1dTvQj7GD9rNM0K38NoYCI8EzAqUX6H/ 2To0YAshEMSda8/Y+UERATCvMLfJV70US45uPwfpfYo24Gdn6mGWraTJQK9jJncMx4Cu AXxKlloOkTSFg+I364/Jh2LmcqnKzf71dOCHwafpQOoXzqRgjwcZKFeu/XqxfuajMgRG qxesgPmaf+emT9NcNdVv2Fz9/a2YNxNyGkrsKXy3n6YTGWDxsJiW545HzcHaMPgzbBX4 UpXg== X-Gm-Message-State: APzg51B3zYFplF3PYTKHBxEyKbpkYB+3dWQFahwTzvxnVxXEwQPbQq60 OprfFp5weE5+I2RcQ8XMnKojCgvvrKjDQXY53ZTc4g== X-Google-Smtp-Source: ANB0VdbQXEclhCFLZcaacx7xRi6XPHqJ5SfEf1QrFHBp/jvbEshFiPdetAvGLXU88u3OW1GpWg3bKYOHFeYZWU8WJ2g= X-Received: by 2002:a2e:6e04:: with SMTP id j4-v6mr7766427ljc.61.1535638083897; Thu, 30 Aug 2018 07:08:03 -0700 (PDT) MIME-Version: 1.0 References: <20171215143456.278a3dc31bb09c9217e83927@aei.mpg.de> <30015_1513349242_5A33E07A_30015_587_1_20171215154659.c8a7f21317a06ab64e480955@aei.mpg.de> <20180830090941.0b92d2012406299b19a68be2@aei.mpg.de> <20180830154404.5da83b6ff0481b17cd6d044e@aei.mpg.de> In-Reply-To: <20180830154404.5da83b6ff0481b17cd6d044e@aei.mpg.de> From: Alan Somers Date: Thu, 30 Aug 2018 08:07:52 -0600 Message-ID: Subject: Re: Fw: 100.chksetuid handging on nfs mounts To: =?UTF-8?B?R2Vycml0IEvDvGhu?= Cc: FreeBSD Net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Aug 2018 14:08:11 -0000 Well that's not very illuminating. I was wondering if it had weird mount options or something. Are you sure that's why find is hanging? What happens if you unmount and repeat the command? On Thu, Aug 30, 2018 at 7:44 AM Gerrit K=C3=BChn = wrote: > On Thu, 30 Aug 2018 07:25:54 -0600 Alan Somers wrot= e > about Re: Fw: 100.chksetuid handging on nfs mounts: > > > > Any ideas why this happens (and how to prevent it)? > > > I just checked, and on my system find does not descend into NFS > > directories mounted under /net. Could you share the output of "mount" = ? > > This is the relevant mount: > > --- > hellpool:/samqfs/FC5/Gerrit on /net/hellpool (nfs, noatime) > --- > > All other mount points under /net are not mounted right now. > > > cu > Gerrit >