NetBSD Problem Report #46132

From dholland@macaran.localdomain  Sat Mar  3 01:00:07 2012
Return-Path: <dholland@macaran.localdomain>
Received: from ( [])
	by (Postfix) with ESMTP id 2EB5B63DFA6
	for <>; Sat,  3 Mar 2012 01:00:07 +0000 (UTC)
Message-Id: <20120303010015.255C16E217@macaran.localdomain>
Date: Fri,  2 Mar 2012 20:00:15 -0500 (EST)
Subject: spurious EINTRs from nfs
X-Send-Pr-Version: 3.95

>Number:         46132
>Category:       kern
>Synopsis:       spurious EINTRs from nfs
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Mar 03 01:05:00 +0000 2012
>Last-Modified:  Sun Jan 01 01:20:01 +0000 2017
>Originator:     David A. Holland
>Release:        NetBSD 6.99.3 (20120227)
System: NetBSD macaran 6.99.3 NetBSD 6.99.3 (MACARAN) #11: Mon Feb 27 17:12:40 EST 2012 dholland@macaran:/usr/src/sys/arch/amd64/compile/MACARAN amd64
Architecture: x86_64
Machine: amd64

I just saw this:

macaran% rm -r vnlock-real
rm: vnlock-real/.hg/store/data/sys/dist/acpica/acmacros.h.i: Interrupted system call
rm: vnlock-real/.hg/store/data/sys/dist/acpica/acnames.h.i: Interrupted system call
rm: vnlock-real/.hg/store/data/sys/dist/acpica: Directory not empty
rm: vnlock-real/.hg/store/data/sys/dist: Directory not empty
rm: vnlock-real/.hg/store/data/sys: Directory not empty
rm: vnlock-real/.hg/store/data: Directory not empty
rm: vnlock-real/.hg/store: Directory not empty
rm: vnlock-real/.hg: Directory not empty
rm: vnlock-real: Directory not empty
Exit 1

This was an old NetBSD source tree stored in Mercurial, on an NFS
volume stored on a NetApp filer across a routed TCP connection. The
system wasn't *entirely* idle while this was going on, but I'm certain
nothing was sending signals to rm and nothing else was using the same
NFS volume locally either.

The thing that sets this particular rm -r apart from others is that
this tree hadn't been touched in years; it took a long time to delete
and I expect the filer had moved the data to the boneyard in some

So I'm guessing there's something in the NFS client code that timed
out and that these timeouts are producing EINTR instead of a sensible
error condition.


Probably can't be repeated on demand. I do have some more comparably
old trees I found today, but I'd just as soon nuke them now rather
than save them for testing.

torches and pitchforks?

From: David Holland <>
Subject: Re: kern/46132: spurious EINTRs from nfs
Date: Sun, 1 Jan 2017 01:17:47 +0000

 On Sat, Mar 03, 2012 at 01:05:00AM +0000, wrote:
  > macaran% rm -r vnlock-real
  > rm: vnlock-real/.hg/store/data/sys/dist/acpica/acmacros.h.i: Interrupted system call

 I still see this from time to time, if anything more than in 2012.

 It remains unclear whether it's really a timeout masquerading as a
 signal, or a filer problem, or what.

 (because the performance of our department infrastructure seems to be
 worse every year, probably as an excuse to eventually outsource

  > >Fix:
  > torches and pitchforks?

 yes please :-)

 David A. Holland

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD:,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.