Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Aug 2018 09:09:41 +0200
From:      Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit.kuehn@aei.mpg.de>
To:        Gerrit =?ISO-8859-1?Q?K=FChn?= <gerrit.kuehn@aei.mpg.de>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>, Alan Somers <asomers@freebsd.org>
Subject:   Re: Fw: 100.chksetuid handging on nfs mounts
Message-ID:  <20180830090941.0b92d2012406299b19a68be2@aei.mpg.de>
In-Reply-To: <30015_1513349242_5A33E07A_30015_587_1_20171215154659.c8a7f21317a06ab64e480955@aei.mpg.de>
References:  <20171215143456.278a3dc31bb09c9217e83927@aei.mpg.de> <CAOtMX2jsQDQ3Csa5qszNMZQbx1cR=EcaPOY15T_QimnkM4%2BCWQ@mail.gmail.com> <30015_1513349242_5A33E07A_30015_587_1_20171215154659.c8a7f21317a06ab64e480955@aei.mpg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Dec 2017 15:46:59 +0100 Gerrit K=FChn <gerrit.kuehn@aei.mpg.de>
wrote about Re: Fw: 100.chksetuid handging on nfs mounts:

Hello all,

Sorry for picking this up after such a long time...

> > This is a known bug.  It happens when an NFS filesystem is mounted on
> > the same mountpoint as a local filesystem.  It's fixed by [1] and
> > MFCed by [2] and [3].  What version are you using?
>=20
> ~ # freebsd-version
> 10.3-RELEASE-p17
>=20
> > [1] https://svnweb.freebsd.org/base?view=3Drevision&revision=3D306048
> > [2] https://svnweb.freebsd.org/base?view=3Drevision&revision=3D306642
> > [3] https://svnweb.freebsd.org/base?view=3Drevision&revision=3D306644
>=20
> Looks like 10.3 didn't get this fix, but 10.4 has it. The system is due
> for an update, anyway. Thanks for the pointers!

The system is running 11.1 meanwhile, and has the fixes mentioned above (I
just checked this again). However, an unavailable nfs server (some
directories simply mounted under /net) still makes it hang on this command
(from ps aux):

---
root  51860   0.0  0.0   8364  2672  -  D    00:07         0:00.24 find
-sx / /dev/null ( ! -fstype local ) -prune -o -type f ( ( ! -perm +010
-and -perm +001 ) -or ( ! -perm +020 -and -perm +002 ) -or ( ! -perm +040
-and -perm +004 ) ) -exec ls -liTd {} +
---

Any ideas why this happens (and how to prevent it)?


cu
  Gerrit



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180830090941.0b92d2012406299b19a68be2>