From: Hans de Bruin <bruinjm-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
To: kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: root on nfs or other troubles
Date: Wed, 25 Mar 2009 22:53:04 +0100 [thread overview]
Message-ID: <49CAA7C0.3040109@xs4all.nl> (raw)
The setup I have here at home consists of a nfs server, and two disk
less clients. Every day the nfs server creates a fresh kernel for the
clients. One of the clients has been inactive for a while (about half a
year) and is now annoyingly unstable. Either the hardware or the kernel
or something else has degraded. The client seams to hang on a nfs
action. The mouse keeps moving when in X, and some screen objects
respond to mouse movement. When in terminal mode (I don't trust the
openchrome x driver) key strokes end up on the terminal. Pinging the
client from another machine ends in timeouts.
I have pinged the client for an hour or two. no problem. Ran several
ping -A's as root, no problem. Ran a normal ping and a 'find / -name
bhjfihreibu -print' and within minutes the ping died.
I could try an older kernel, say about half a year ago, but things have
changed in haf a year like the kernel verion of the nfs server, nfs
parmeters and kernel .config file. The second client (different
hardware) is as stable as a rock.
Al the kernel options under kernel hacking in make menuconfig are off.
Is there any that I would want to turn on?
--
Hans
next reply other threads:[~2009-03-25 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 21:53 Hans de Bruin [this message]
[not found] ` <49CAA7C0.3040109-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2009-03-30 20:39 ` root on nfs or other troubles Hans de Bruin
[not found] ` <49D12DF4.7040902-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2009-04-04 17:22 ` Hans de Bruin
[not found] ` <49D79749.3060906-qWit8jRvyhVmR6Xm/wNWPw@public.gmane.org>
2009-04-05 16:02 ` Hans de Bruin
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=49CAA7C0.3040109@xs4all.nl \
--to=bruinjm-qwit8jrvyhvmr6xm/wnwpw@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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.