public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Holmes <jholmes@psu.edu>
To: Douglas Furlong <douglas.furlong@firebox.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS stops responding
Date: Wed, 13 Oct 2004 11:07:07 -0400	[thread overview]
Message-ID: <416D449B.7060908@psu.edu> (raw)
In-Reply-To: <1097146611.4160.24.camel@douglas-furlong.firebox.com>

Douglas Furlong wrote:
> On Fri, 2004-10-01 at 11:40 -0400, Jason Holmes wrote:
> 
>>FYI, I'm beginning to suspect that this is a problem more with the newer 
>>RedHat kernels than anything else.  I've only had one vanilla kernel NFS 
>>lockup since I moved the NFS servers to 2.6.8.1 (3 days) and that 
>>happened right after I did the move, so it could be coincidental.  Back 
>>when the servers ran RedHat kernels, the RedHat kernel clients never 
>>locked up whereas the vanilla clients did.  Yesterday I had 4 NFS 
>>lockups on the same machine running the RedHat 2.4.21-20.ELsmp kernel 
>>(the one that generated the trace below), but it hasn't locked up since 
>>I moved it to 2.6.8.1.  I guess I'll know for sure if my lockups don't 
>>come back for a week or so.
>>
>>Thanks,
> 
> <snip>
> 
> Have you had any more lockups?
> 
> Would you feel happy entering a bugzilla entry for this problem over at
> redhat? You seem to have got a lot more information then I have in my
> trouble shooting, I will then add what ever else I have, and my local
> setup.

I'm sorry to say that I had my first lockup this morning after a week 
and a half of no problems.  I was unfortunately unable to get any 
debugging information from it at the time.  This was a 2.4.27 client 
against a 2.6.8.1 server.

Thanks,

--
Jason Holmes


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-10-13 15:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 13:39 NFS stops responding Douglas Furlong
2004-09-30 16:06 ` Jason Holmes
2004-09-30 19:10   ` Jason Holmes
2004-10-01 15:40     ` Jason Holmes
2004-10-07 10:56       ` Douglas Furlong
2004-10-13 15:07         ` Jason Holmes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-04-14 21:06 Michael O'Donnell
2010-04-15 18:04 ` J. Bruce Fields
2010-04-17  0:17 ` Dennis Nezic
     [not found]   ` <20100416201700.215b0bea.dennisn-YN8wfZw00oOZ9vWoFJJngh2eb7JE58TQ@public.gmane.org>
2010-04-19 14:34     ` Michael O'Donnell
     [not found]       ` <4BCC69E4.70405-kx56TfycDUc@public.gmane.org>
2010-04-22 15:19         ` Dennis Nezic
2010-04-28 15:51           ` Dennis Nezic

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=416D449B.7060908@psu.edu \
    --to=jholmes@psu.edu \
    --cc=douglas.furlong@firebox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox