All of lore.kernel.org
 help / color / mirror / Atom feed
From: Judith Flo Gaya <jflo@imppc.org>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: problem with nfs latency during high IO
Date: Tue, 15 Mar 2011 17:25:46 +0100	[thread overview]
Message-ID: <4D7F930A.1010509@imppc.org> (raw)

[Sorry if the e-mail appears to be duplicated, I don't see it in the 
list, but I sent it 3 days ago ;(]

Hello,

I was told some days ago that my problem with my NFS system is related 
to this bug, as the problem that I'm experiencing is quite similar.

The bug : https://bugzilla.redhat.com/show_bug.cgi?id=469848

The link itself explains quite well my issue, I'm just truing to copy a 
big file (36Gb) to my nfs server and when I try to get an ls -l command 
to the same folder where I'm copying data, the command gets stuck for 
some time. This amount of time changes from a few secs to SOME minutes 
(9' is the current record).
I can live with some seconds of delay, but minutes is something quite 
unacceptable.

As this is an nfs server running on a red hat system (an HP ibrix x9300 
with Red Hat 5.3 x86_64, kernel 2.6.18-128) I was told to apply the 
patch suggested from the bug on my clients.

Unfortunately my clients are running fedora core 14 (x86_64, kernel 
2.6.35.6-45) and I can't find the file that they are referring to, the 
file fs/nfs/inode.c is not there and I can't find the rpm that contains it.

As the bug is a very very old one, I took it for granted that is already 
applied to fedora, but I wanted to make sure that it is looking at the file.

Can you help me on this? I'm I wrong in my supposition (is the patch 
really applied)? is it possible that my problem is somewhere else?

Thanks a lot in advance for your help, please let me know if I can 
provide any more information.
j



             reply	other threads:[~2011-03-15 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 16:25 Judith Flo Gaya [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-12 12:58 problem with nfs latency during high IO Judith Flo Gaya
2011-03-15 16:24 ` Chuck Lever
2011-03-15 17:25   ` Judith Flo Gaya
2011-03-15 18:03     ` Chuck Lever
2011-03-15 18:15       ` Chuck Lever
2011-03-17  1:21         ` Harshula Jayasuriya
2011-03-15 21:33       ` Judith Flo Gaya
2011-03-15 21:28         ` Chuck Lever
2011-03-15 21:58           ` Judith Flo Gaya
2011-03-15 22:10             ` Chuck Lever
2011-03-16 11:45               ` Judith Flo Gaya
2011-03-16 13:24                 ` Chuck Lever
2011-03-16 13:42                   ` peter.staubach
2011-03-16 15:18                   ` Jim Rees
2011-03-16 15:31                     ` Jim Rees
2011-03-16 16:52                       ` Judith Flo Gaya
2011-03-16 23:51                 ` Simon Kirby

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=4D7F930A.1010509@imppc.org \
    --to=jflo@imppc.org \
    --cc=linux-nfs@vger.kernel.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.