From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Michal Sabala <lkml@saahbs.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.18 mmap hangs unrelated apps
Date: Fri, 15 Dec 2006 11:24:15 -0500 [thread overview]
Message-ID: <1166199855.5761.34.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20061215023014.GC2721@prosiaczek>
On Thu, 2006-12-14 at 20:30 -0600, Michal Sabala wrote:
> Hello LKML,
>
> I am observing processes entering uninterruptible sleep apparently due
> to an unrelated application using mmap over nfs. Applications in
> "uninterruptible sleep" hang indefinitely while other applications
> continue working properly.
>
> The code causing the mmap nfs hangs does the following:
> (as replicated by the included test-mmap.c file)
>
> 1. create file on nfs (file_A, descr_A)
> 2. make file_A a sparse 200MB file
> 3. mmap descr_A
> 4. close descr_A
> 5. unlink file_A
> 6. memcpy 200MB to mmaped buffer
> 7. create a second file on nfs (file_B, descr_B)
> 8. write() 200MB from mmaped buffer to descr_B
> 9. close descr_B
> 10. munmap first file
>
> This code may need to be ran tens to hundred runs to trigger the condition.
>
> During the execution of the above code, unrelated applications enter
> uninterruptible sleep (D) - usually firefox2.0, Xorg/XFree86, gimp2.2, gconfd
> or bash; probably the most active processes.
>
> `dmesg` shows nothing of interest.
>
> `free` shows anywhere between 1MB and 80MB of memory still remaining
> free when the problem occurs.
>
> `cat /proc/*PID*/wchan` for all hanging processes contains page_sync.
Have you tried an 'echo t >/proc/sysrq-trigger' on a client with one of
these hanging processes? If so, what does the output look like?
Cheers
Trond
next prev parent reply other threads:[~2006-12-15 16:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 2:30 Michal Sabala
2006-12-15 16:24 ` Trond Myklebust [this message]
2006-12-15 17:50 ` Michal Sabala
2006-12-15 19:44 ` Trond Myklebust
2006-12-15 21:06 ` Michal Sabala
2006-12-15 21:12 ` Arjan van de Ven
2006-12-15 21:43 ` Michal Sabala
2006-12-15 21:44 ` Trond Myklebust
2006-12-15 22:05 ` Michal Sabala
2006-12-19 22:26 ` Andrew Morton
2006-12-19 23:19 ` Trond Myklebust
2006-12-20 0:03 ` Andrew Morton
2006-12-20 0:17 ` Trond Myklebust
2006-12-20 0:22 ` Andrew Morton
2006-12-20 1:21 ` Trond Myklebust
2007-01-08 14:48 ` [PATCH] NFS: Fix race in nfs_release_page() Peter Zijlstra
2006-12-20 14:51 ` 2.6.18 mmap hangs unrelated apps Michal Sabala
2006-12-15 20:42 ` Andrew Morton
2006-12-15 21:35 ` Michal Sabala
2006-12-15 21:41 ` Andrew Morton
2006-12-16 12:59 ` Christian Kuhn
2006-12-16 18:45 ` Christian Kuhn
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=1166199855.5761.34.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@saahbs.net \
/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
all inboxes | Powered by JetHome®