All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Rose <krose+linuxnfs@krose.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Tue, 09 Dec 2003 15:09:22 -0500	[thread overview]
Message-ID: <87ekvdpxcd.fsf@nausicaa.krose.org> (raw)
In-Reply-To: <3FD626ED.1010100@RedHat.com> (Steve Dickson's message of "Tue, 09 Dec 2003 14:47:57 -0500")

Steve Dickson <SteveD@redhat.com> writes:

> This is happening on a Fedora Core kernel, right?

No, this is a vanilla 2.6.0-test11.  Upon review of my email, I can't
believe I didn't mention the kernel version. :)

> If so, Could you send me the exact steps you do to cause this
> to happen....

Certainly.  Compile and reboot.  NFS comes up, after which SFS comes
up:

  /opt/sfs/bin/sfscd

Then, I log in as krose and

  cd music

where music is a symlink to
sfs/kushana.valley-of-wind.krose.org/music, the first two parts of
which are a symlink to
/sfs/@kushana.valley-of-wind.krose.org,jc72upywax7dsvd7rwpbvrfwpq4j2w7e.
So, in effect, I end up in
/sfs/@kushana.valley-of-wind.krose.org,jc72upywax7dsvd7rwpbvrfwpq4j2w7e/music.

Then I type ls, and get a segfault and an oops in dmesg.  (Sometimes,
it succeeds the first time, but always segfaults when I perform the
same steps a few minutes later.)  After this, NFS and/or SFS appear to
be wedged in a bad state, because future requests to SFS don't work.
Stopping SFS is a no-go, either.

I'm not really sure what kind of detail you're looking for, so please
feel free to be more specific if you want/need more information.

Cheers,
Kyle


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-12-09 20:09 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07   ` Douglas Furlong
2003-11-27 20:02     ` Trond Myklebust
2003-11-28  8:46 ` Juergen Sauer
2003-11-28  9:37   ` Douglas Furlong
2003-11-28 10:11     ` Juergen Sauer
2003-11-28 10:48       ` Douglas Furlong
2003-11-28 12:28         ` Bogdan Costescu
2003-11-28 16:56           ` Trond Myklebust
2003-11-28 18:43             ` Bogdan Costescu
2003-12-02 14:37             ` Douglas Furlong
2003-12-02 15:37               ` Trond Myklebust
2003-12-04 17:17                 ` Steve Dickson
2003-12-04 17:37             ` Steve Dickson
2003-12-04 18:39               ` Trond Myklebust
2003-12-04 19:11                 ` Steve Dickson
2003-12-04 20:55                   ` seth vidal
2003-12-04 21:24                     ` Steve Dickson
2003-12-05  2:53                       ` Kyle Rose
2003-12-09 19:47                         ` Steve Dickson
2003-12-09 20:09                           ` Kyle Rose [this message]
2003-12-05 15:50                 ` Bogdan Costescu
2003-11-30 20:01           ` seth vidal
2003-12-01 10:58             ` Bogdan Costescu
2003-11-28 12:36       ` Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2004-07-30 17:09 nfs " Pavel Bartusek
2009-05-16  0:57 nfs: " Jerome Walters

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=87ekvdpxcd.fsf@nausicaa.krose.org \
    --to=krose+linuxnfs@krose.org \
    --cc=SteveD@redhat.com \
    --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.