LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: samg@seven4sky.com
To: "Jaco Kroon" <jkroon@cs.up.ac.za>
Cc: linux-kernel@vger.kernel.org, acooks@cs.up.ac.za
Subject: Re: NFS deadlock
Date: Wed, 19 May 2004 12:09:20 -0400 (EDT) [thread overview]
Message-ID: <1231.128.150.143.219.1084982960.squirrel@webmail.seven4sky.com> (raw)
In-Reply-To: <40A9E239.4010909@cs.up.ac.za>
Jaco,
How are your boxes locking up, I have nfs in use every day,
does rpc die?
what kernel are you using?
and are you transfering linux to linux, or to some other platform.
The only time I had problems was when my client locked up
because I disconnected the server, and it hung the client,
the only solution (based on the way I connected), was to reboot.
To make matters worse, I rean a script that used du every day, and
so there were 12+ instances of du, all trying to run about.
I would suggest using a program like sysstat, or sar, to help you
analyse the issues at hand.
-sam
> Hello there
>
> I've once again got problems with the kernel locking up. I'm now
> convinced that it has something to do with NFS.
>
> Previously weve had 2 machines that locked up, plus my one at home,
> resulting in three machines. Sometimes they would recover by themselves
> after some time, other times they could be left for 2 days or so without
> recovering. All three of these use NFS to export files to other
> machines, it's the only thing we can find they have in common, other
> that x86 architecture, but then other machines would be dying as well.
> It should be noted that none of these runs on the newest hardware, but
> that should not matter, neither does any of our other servers. We have
> a 3rd NFS server, which doesn't take nearly as heavy load via NFS. I've
> been wondering why it hasn't locked up either, and this morning (right
> now in fact) it has decided that it is it's turn and is currently
> unusable.
>
> If anybody else is experiencing similar problems, or have possible work
> arounds, it would be appreciated if you could share your knowledge.
>
> Jaco
>
> ===========================================
> This message and attachments are subject to a disclaimer. Please refer to
> www.it.up.ac.za/documentation/governance/disclaimer/ for full details.
> Hierdie boodskap en aanhangsels is aan 'n vrywaringsklousule onderhewig.
> Volledige besonderhede is by
> www.it.up.ac.za/documentation/governance/disclaimer/ beskikbaar.
> ===========================================
>
>
next prev parent reply other threads:[~2004-05-19 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:15 Jaco Kroon
2004-05-19 16:09 ` samg [this message]
2004-05-20 8:10 ` Jaco Kroon
2004-05-20 14:46 ` Sam Gill
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=1231.128.150.143.219.1084982960.squirrel@webmail.seven4sky.com \
--to=samg@seven4sky.com \
--cc=acooks@cs.up.ac.za \
--cc=jkroon@cs.up.ac.za \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: NFS deadlock' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).