From: Michael Buesch <fsdeveloper@yahoo.de>
To: pwitting@Cyveillance.com
Cc: nfs@lists.sourceforge.net
Subject: Re: processes stuck in D state
Date: Tue, 6 May 2003 19:31:00 +0200 [thread overview]
Message-ID: <200305061931.14023.fsdeveloper@yahoo.de> (raw)
In-Reply-To: <D38AFB3080F3D311807300B0D0203E53033A9572@MERCURY>
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday 06 May 2003 19:09, pwitting@Cyveillance.com wrote:
> Actually, I have seen this on the server before, specifically
> When using an older version of IBM's JFS for Linux with RH 7.3
I'm running ext3 on the server.
> I worked with the JFS team and JFS v1.1.0 and kernel 2.4.20
> seemed to stabilize it, at least I've seen no more "freezes"
> as a result.
server-kernel is 2.4.21-pre6.
> Judging by your mail address this might be your
> problem as well.
You refer to the "fs" in my e-mail address? :)
The "fs" stands for "FreeSoftware".
> One noticeable symptom is that cd'ing to an affected dir and
> attempting an ls would also freeze (I had a large (20GB+) file
> copy going, so I usually knew what the affected dir was.
>
> Two other things that helped:
> 1) increasing the # of nfs threads (120 or more)
> 2) ensuring the uid/gid the remote thread was using existed on
> the server. (sounds stupid but it helped)
>
> neither "cured" the issue, but it went from being reproducible
> to being occasional.
>
> Good Luck.
thanks. :)
=2D --=20
Regards Michael B=FCsch
http://www.8ung.at/tuxsoft
19:26:58 up 3:18, 2 users, load average: 1.01, 1.08, 1.05
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+t/FhoxoigfggmSgRAqgLAJ9hGo5l2c1y/oiZxamh/M88avZYIwCggzTc
lgyMmTHSGnxK17Xfq1Vb/eg=3D
=3DNi5P
=2D----END PGP SIGNATURE-----
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-06 17:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 17:09 processes stuck in D state pwitting
2003-05-06 17:31 ` Michael Buesch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 16:33 Processes " Olaf Kirch
2003-05-06 18:32 processes " Guolin Cheng
2003-05-06 15:47 Lever, Charles
2003-05-06 15:18 Lever, Charles
2003-05-06 14:51 Michael Buesch
2003-05-06 15:20 ` Trond Myklebust
2003-05-06 15:41 ` Michael Buesch
2003-05-06 16:05 ` Trond Myklebust
2003-05-06 16:30 ` Michael Buesch
2003-05-06 16:54 ` Trond Myklebust
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=200305061931.14023.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--cc=nfs@lists.sourceforge.net \
--cc=pwitting@Cyveillance.com \
/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