All of lore.kernel.org
 help / color / mirror / Atom feed
From: michael <michael@newdream.net>
To: nfs@lists.sourceforge.net
Subject: statd segfaults
Date: Mon, 17 Feb 2003 22:55:04 -0800	[thread overview]
Message-ID: <3E51D8C8.8000905@newdream.net> (raw)

statd segfaults and has to be restarted.

Has anyone else experienced this behavior? have any suggestions? I have 
been able to find references to the problem in various list archives, 
but haven't been able to find a solution.

i can provide more information if need be.

thanks in advance,
michael

----

client:
debian 3.0
nfs-common_1.0.2-1_i386.deb
kernels: 2.2.19, 2.2.23, 2.4.20 using nfs patches and not

snipit from /etc/fstab:
10.7.99.15:/vol/vol0/swarthy/russian    /home/.russian  nfs 
defaults,intr,vers=3,rsize=8192,wsize=8192,bg   0 0
10.7.99.93:/vol/vol2/crummy/localbackups/medina /mnt/filerbackup 
nfs     defaults,intr,vers=3,rsize=8192,wsize=8192,bg   0 0
10.7.99.92:/vol/vol1/frothy/kindle      /home/.kindle   nfs 
defaults,intr,vers=3,rsize=8192,wsize=8192,bg   0 0


server:
Netapp F760 OS 6.3

the problem is happening on many machines with statd dying after 
anywhere from minutes to days.  I can include a complete strace if it 
would be useful... for now here are the last few lines of two:

1:

ioctl(6, 0x8913, 0xbffff5fc)            = 0
ioctl(6, 0x8915, 0xbffff5fc)            = 0
ioctl(6, 0x8913, 0xbffff5fc)            = 0
ioctl(6, 0x8915, 0xbffff5fc)            = 0
ioctl(6, 0x8913, 0xbffff5fc)            = 0
ioctl(6, 0x8915, 0xbffff5fc)            = 0
ioctl(6, 0x8913, 0xbffff5fc)            = 0
ioctl(6, 0x8915, 0xbffff5fc)            = 0
close(6)                                = 0
open("/var/lib/nfs/sm/10.7.99.14", O_WRONLY|O_CREAT|O_SYNC, 0600) = 6
close(6)                                = 0
time([1039462404])                      = 1039462404
write(2, "12/09/2002 11:33:24 rpc.statd[29"..., 7412/09/2002 11:33:24 
rpc.statd[29998]: MONITORING 10.7.99.14 for 127.0.0.1
) = 74
sendmsg(4, {msg_name(16)={sin_family=AF_INET, sin_port=htons(2670), 
sin_addr=inet_addr("127.0.0.1")}}, 
msg_iov(1)=[{"\336^\313\2\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
32}], msg_controllen=24, msg_control=0x8051c20, , msg_flags=0}, 0) = 32
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


2:

ioctl(6, 0x8915, 0xbffff60c)            = 0
ioctl(6, 0x8913, 0xbffff60c)            = 0
ioctl(6, 0x8915, 0xbffff60c)            = 0
ioctl(6, 0x8913, 0xbffff60c)            = 0
ioctl(6, 0x8915, 0xbffff60c)            = 0
ioctl(6, 0x8913, 0xbffff60c)            = 0
ioctl(6, 0x8915, 0xbffff60c)            = 0
ioctl(6, 0x8913, 0xbffff60c)            = 0
ioctl(6, 0x8915, 0xbffff60c)            = 0
ioctl(6, 0x8913, 0xbffff60c)            = 0
ioctl(6, 0x8915, 0xbffff60c)            = 0
close(6)                                = 0
open("/var/lib/nfs/sm/10.7.99.93", O_WRONLY|O_CREAT|O_SYNC, 0600) = 6
close(6)                                = 0
time([1039462125])                      = 1039462125
write(2, "12/09/2002 11:28:45 rpc.statd[70"..., 7312/09/2002 11:28:45 
rpc.statd[7097]: MONITORING 10.7.99.93 for 127.0.0.1
) = 73
sendmsg(4, {msg_name(16)={sin_family=AF_INET, sin_port=htons(1475), 
sin_addr=inet_addr("127.0.0.1")}}, 
msg_iov(1)=[{"\220\370\362\17\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 
32}], msg_controllen=24, msg_control=0x8050fb0, , msg_flags=0}, 0) = 32
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


-----
keywords: statd dies dying segfault debian woody netapp nfs-common



-------------------------------------------------------
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

             reply	other threads:[~2003-02-18  6:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18  6:55 michael [this message]
2003-02-18  9:30 ` statd segfaults Trond Myklebust
2003-02-19  0:08   ` Neil Brown
2003-04-08 20:01     ` michael
2003-04-09  0:56       ` Neil Brown
2003-04-11  0:57         ` michael
2003-04-08 20:05     ` michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E51D8C8.8000905@newdream.net \
    --to=michael@newdream.net \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.