From: michael Subject: Re: repeatable statd segfault Date: Thu, 04 Sep 2003 20:23:12 -0700 Sender: nfs-admin@lists.sourceforge.net Message-ID: <3F5801A0.40301@hq.newdream.net> References: <3F57FC44.9070208@hq.newdream.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Return-path: Received: from sc8-sf-mx1-b.sourceforge.net ([10.3.1.11] helo=sc8-sf-mx1.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Cipher TLSv1:DES-CBC3-SHA:168) (Exim 3.31-VA-mm2 #1 (Debian)) id 19v7DR-0008Q3-00 for ; Thu, 04 Sep 2003 20:24:53 -0700 Received: from smaug.dreamhost.com ([66.33.209.15] ident=postfix) by sc8-sf-mx1.sourceforge.net with esmtp (Exim 4.22) id 19v7DQ-00029q-Lt for nfs@lists.sourceforge.net; Thu, 04 Sep 2003 20:24:52 -0700 Received: from hq.newdream.net (inez.hq.newdream.net [66.33.200.139]) by smaug.dreamhost.com (Postfix) with ESMTP id D8D7E5B79E for ; Thu, 4 Sep 2003 20:24:22 -0700 (PDT) To: nfs List In-Reply-To: <3F57FC44.9070208@hq.newdream.net> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: Here is a slight variation of the segfault. in this case locking worked for about 5-10 minutes, then upon a test suddenly... (note: this is a slightly older version of statd.) (gdb) run -Fd The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /sbin/rpc.statd -Fd (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)... 09/04/2003 20:03:58 rpc.statd[18964]: Version 1.0 Starting 09/04/2003 20:03:58 rpc.statd[18964]: Flags: No-Daemon Log-STDERR 09/04/2003 20:03:58 rpc.statd[18964]: New state: 15471 09/04/2003 20:03:58 rpc.statd[18964]: Waiting for reply... (timeo 5) 09/04/2003 20:03:58 rpc.statd[18964]: Waiting for reply... (timeo 5) 09/04/2003 20:03:58 rpc.statd[18964]: Notification of 10.7.10.8 succeeded. 09/04/2003 20:03:58 rpc.statd[18964]: Unlinked /var/lib/nfs/sm.bak/10.7.10.8 09/04/2003 20:03:58 rpc.statd[18964]: Waiting for client connections. 09/04/2003 20:18:11 rpc.statd[18964]: Received SM_UNMON request from gir for 10.7.10.8 while not monitoring any hosts. (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x40122e3a in svc_getreqset () from /lib/libc.so.6 (gdb) michael wrote: > (gdb) run -Fd > > Starting program: /usr/local/src/nfs-utils-1.0.5/utils/statd/statd -Fd > 09/04/2003 19:44:57 statd[12873]: Version 1.0.5 Starting > 09/04/2003 19:44:57 statd[12873]: Flags: No-Daemon Log-STDERR > 09/04/2003 19:44:57 statd[12873]: statd running as root. chown > /var/lib/nfs/sm to choose different user > > 09/04/2003 19:44:57 statd[12873]: New state: 15467 > 09/04/2003 19:44:57 statd[12873]: Waiting for client connections. > > --> at this point i run ./testlk /home/.raby/nfs_lock_test/blah > --> the file is mounted on a netapp 760 and the following happens: > > > --- Begin notify list dump --- > Entry 1: 10.18.34.19 > --- End notify list dump --- > 09/04/2003 19:45:12 statd[12873]: MONITORING 10.18.34.19 for gir > > Program received signal SIGSEGV, Segmentation fault. > 0x40119e3a in svc_getreqset () from /lib/libc.so.6 > (gdb) ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs