Fw: 100.chksetuid handging on nfs mounts
Gary Palmer
gpalmer at freebsd.org
Fri Aug 31 11:33:06 UTC 2018
On Fri, Aug 31, 2018 at 08:29:33AM +0200, Gerrit K?hn wrote:
> On Thu, 30 Aug 2018 08:07:52 -0600 Alan Somers <asomers at freebsd.org> wrote
> about Re: Fw: 100.chksetuid handging on nfs mounts:
>
> > 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?
>
> I just tried these things:
>
> find command with nfs mounted and connection working: runs fine
> find command with nfs unmounted: runs fine
> find command with nfs mounted and nfs-nic down: hangs
>
> As soon as I "up" the interface again, find continues to run:
>
> ---
> root at crest:/ # 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 \{\} \+
> nfs server hellpool:/samqfs/FC5/Gerrit: not responding
> nfs server hellpool:/samqfs/FC5/Gerrit: is alive again
> root at crest:/ #
You might want to retry the experiment but look at the state of the
find process using "ps alxww" or similar, or use ktrace to figure out
what it is doing. With the '-x' flag to not cross mount points I suspect
it is using stat(2) on the mount point to check to see if the st_dev
field changes, and then skip that directory if it is different. With
the NFS server unreachable the stat(2) cannot complete.
Regards,
Gary
More information about the freebsd-net
mailing list