From owner-freebsd-current Tue Oct 22 18:18:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CDF637B401 for ; Tue, 22 Oct 2002 18:18:52 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 985F743E7B for ; Tue, 22 Oct 2002 18:18:51 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.6/8.12.5) id g9N1Ijaj038335; Tue, 22 Oct 2002 20:18:45 -0500 (CDT) (envelope-from dan) Date: Tue, 22 Oct 2002 20:18:44 -0500 From: Dan Nelson To: Daniel Rock Cc: current@FreeBSD.ORG Subject: Re: file system deadlock in -CURRENT Message-ID: <20021023011842.GA13334@dan.emsphone.com> References: <3DB5D235.6090403@t-online.de> <3DB5D5AB.3060404@t-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DB5D5AB.3060404@t-online.de> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Oct 23), Daniel Rock said: > Daniel Rock schrieb: > >I found an interesting problem during tracing my perl-5.8 problem I > >mailed some days ago. > > > >Sometimes - I cannot forcibly reproduce this event - while I'm > >trying to truss a process, I first get the following error message: > > > >/usr/ports/lang/perl5.8/work/perl-5.8.0# truss ./perl > >truss: cannot open /proc/44502/mem: No such file or directory > >or the following error message: > >/usr/ports/lang/perl5.8/work/perl-5.8.0# truss ./perl > >truss: PIOCWAIT: Input/output error > > A side note: The problem seems to be related with programs compiled with > profiling enabled. trussing a normal program never showed this behaviour. I have the same problem, but can pretty easily trigger it by trying to truss a setuid binary. Or maybe I always happen to truss setuid binaries. I don't have any programs built with profiling. Anyway, the behaviour is the same. Truss once, get a no such file or directory error. Try again, and cwd is locked. The process hangs either in "inode" or more recently "ufs". -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message