I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.
For further assistance, please contact <postmaster@CC234543-A.vron1.nj.home.com>
If you do so, please include this problem report. You can
delete your own text from the message returned below.
The Postfix program
--- Delivery error report follows ---
<eam@localhost.vron1.nj.home.com>: unknown mail transport error
--- Undelivered message follows ---
Received: from localhost (localhost [127.0.0.1])
by CC234543-A.vron1.nj.home.com (Postfix) with ESMTP id E03144287
for <eam@localhost>; Sun, 25 Jul 1999 21:05:54 -0400 (EDT)
Received: from mail.eclipse.net
by localhost with POP3 (fetchmail-5.0.3)
for eam@localhost (single-drop); Sun, 25 Jul 1999 21:05:54 -0400 (EDT)
Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10])
by mx01.eclipse.net (8.9.1a/8.9.1) with ESMTP id GAA05955
for <eam@eclipse.net>; Fri, 23 Jul 1999 06:21:22 -0400 (EDT)
Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2])
by entropy.muc.muohio.edu (8.8.7/8.8.7) with ESMTP id GAA23535;
Fri, 23 Jul 1999 06:16:26 -0400
Received: by vger.rutgers.edu via listexpand id <S154292AbPGWKOR>;
Fri, 23 Jul 1999 06:14:17 -0400
Received: by vger.rutgers.edu id <S154278AbPGWKOF>;
Fri, 23 Jul 1999 06:14:05 -0400
Received: from smtp2.cinet.es ([194.140.128.73]:30760 "EHLO smtp2.cinet.es")
by vger.rutgers.edu with ESMTP id <S154253AbPGWKNu>;
Fri, 23 Jul 1999 06:13:50 -0400
Received: from angel (ctv21225131005.ctv.es [212.25.131.5])
by smtp2.cinet.es (8.9.2/8.9.2) with SMTP id LAA15066
for <linux-kernel@vger.rutgers.edu>; Fri, 23 Jul 1999 11:18:19 +0200 (CEST)
Received: from (unverified 192.1.1.12) by angel
(S-MailServer 1.2) with SMTP id <B000000000000105.MSG>;
Fri, 23 Jul 1999 12:15:06, Románico Hora estándar
From: "Enrique Bernal" <ebv@a68.com>
To: <linux-kernel@vger.rutgers.edu>
Subject: NFS server and client problems
Date: Fri, 23 Jul 1999 12:12:57 +0200
Message-ID: <000001bed4f3$efb65d00$0c0101c0@a68.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-linux-kernel@vger.rutgers.edu
Precedence: bulk
X-Loop: majordomo@vger.rutgers.edu
X-Orcpt: rfc822;linux-kernel-outgoing-dig
Content-Transfer-Encoding: 7bit
X-UIDL: 79659fd81c0a4d9466432578e3907fdb
Hi, list
Here is my question:
OS: SuSE 6.2 kernel 2.2.5 (In servers and client)
I have a PC running like a nfs-client (called "concentrador") with an
application that have to poll 3 PC's nfs-servers (called "puesto1",
"puesto2", "puesto3") in a continuous loop.
When a nfs-server (for example "puesto2") make a request to the nfs-client
("contrador"), the answer of "concentrador" is so slow (more than 5 o2 10
seconds) that "puesto2" suposes that "concentrador" is down.
Making the same with a PC nfs-client and 2 PC's nfs-servers performance is
OK and there's no problem at all.
The way server and client can communicate is by writing in some files
residents in nfs-server file system (in the exported directory).
I've modified the number of nfs daemons (up to 12 in a PC) (on the client
side and ond the server side).
I've mounted the nfs-servers with differents options:
actimeo=1
actimeo=0
rsize=4096, wsize=4096
But none of this worked.
Looking into /var/log/messages of the nfs-client PC I've found this:
nfs: RPC call returned error 111
RPC: task of released request still queued
RPC: (task is on xprt_pending)
and also this:
kernel: __nfs_fhget: inode 92320 busy, icount=2, inlink=1
kernel: __nfs_free_dentries: found //NEGATIVA.cag, d_count=0, hashed=1
kernel: nfs_dentry_delete: //NEGATIVA.cab; ino=92320, count=2, i_nlink=1
Lots of thanks in advance for your help !
Enrique Bernal
ebv@a68.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/