public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cade.robinson at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12552] New: lstat hangs when trying to stat a file being written to via nfs
Date: Mon, 07 Mar 2011 21:11:00 -0000	[thread overview]
Message-ID: <bug-12552-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12552

           Summary: lstat hangs when trying to stat a file being written
                    to via nfs
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper.fsp@gmail.com
        ReportedBy: cade.robinson@gmail.com


I don't know if this is libc or kernel but I am starting here.

lstat hangs for a few seconds when trying to stat a file being written to via
NFS.

I have tested this with glibc 2.4 (SLES 10), 2.11 (SLES 11, ubuntu 10.04), 2.12
(ubuntu 10.10),  and 2.13 (arch).
I have tested against a Netapp filer and an ubuntu 7.10 NFS server.

SLES9 with glibc 2.3.3 does not exhibit this behavior.


Steps to recreate:
Open two windows to a client mounting something NFS and change to the NFS
mount.
Run in one window:
dd if=/dev/zero of=testfile bs=1024 count=10240000

In the other window run this while the dd is running:
strace stat testfile
or 
strace ls testfile
The strace will hang for a bit on the lstat() system call on the NFS client
that is running the dd (or write).

If you run the strace command on another client at the same time the dd is
running you will get no pause/hang with lstat.

I can see this with anything that runs lstat like ls, stat, a compiled program
that just does an lstat, etc.

Again I don't know if this is glibc or the kernel but I don't know where to
start and this is killing us performance wise.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-03-07 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 21:11 cade.robinson at gmail dot com [this message]
2011-03-08  1:01 ` [Bug libc/12552] " drepper.fsp at gmail dot com
2014-06-27 13:46 ` fweimer at redhat dot com

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=bug-12552-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).