From: Kip Macy <kmacy@fsmware.com>
To: Steven Hand <Steven.Hand@cl.cam.ac.uk>
Cc: Steve Traugott <stevegt@TerraLuna.Org>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net, joyce@TerraLuna.Org,
awclarke@tstt.net.tt
Subject: Re: xenolinux /dev/random
Date: Thu, 13 May 2004 07:54:57 -0700 (PDT) [thread overview]
Message-ID: <20040513075236.B20816@demos.bsdclusters.com> (raw)
In-Reply-To: <E1BOAPR-0001Pu-00@mta1.cl.cam.ac.uk>
Are you also using Linux as an NFS server? We use Linux extensively
in-house for client machines and have not seen this. Although I'm sure
we don't use the default Linux settings.
-Kip
On Thu, 13 May 2004, Steven Hand wrote:
>
> >My goodness! See the message I just now posted to xen-devel about NFS
> >root hangs; could this be what we're hitting? The most recent hang we
> >saw happened while an rsync was running over ssh *and* someone restarted
> >apache...
> >
> >This wouldn't cause the "NFS server not responding/NFS server OK"
> >messages on the domain's console, though (or does that show up as a
> >symptom of this too?)
>
> I don't think this is the cause of the NFS hangs you've been seeing; that
> appears to be a generic linux thing (at least we see it with our regular
> linux boxes as well as with xen boxes); however if you want to test the
> theory the easiest thing to do is to change the /dev/random device node
> to be an alias for /dev/urandom (a non-blocking but potentiallyweaker
> source of randomness).
>
> The /dev/random bug only really manifested for us during boot, only on
> Xen, and resulted in a permanenent hang.
>
> The "NFS server foo not responding" followed by later "NFS server foo OK"
> messages from linux appear to be due to a combination of stupid timeouts
> in the linux sunrpc code and another bug which can cause automounters
> to fall into an uninterruptible sleep. If you check "ps auwwx" on a
> machine which is having problems and notice proceesses in state 'D'
> then this is biting you. Even if this doesn't occur, the crappy timeouts
> in the regular linux code mean that linux perfroms very badly if it gets
> any errors/loss/congestion during nfs operations.
>
> cheers,
>
> S.
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
next prev parent reply other threads:[~2004-05-13 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 8:36 xenolinux /dev/random Ian Pratt
2004-05-13 3:09 ` Steve Traugott
2004-05-13 7:13 ` Steven Hand
2004-05-13 14:54 ` Kip Macy [this message]
2004-05-14 1:42 ` Steve Traugott
2004-05-14 8:03 ` Ian Pratt
2004-05-14 13:57 ` Kip Macy
2004-05-14 14:14 ` Kip Macy
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=20040513075236.B20816@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=Steven.Hand@cl.cam.ac.uk \
--cc=awclarke@tstt.net.tt \
--cc=joyce@TerraLuna.Org \
--cc=stevegt@TerraLuna.Org \
--cc=xen-devel@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.