From: John Hughes <john@Calva.COM>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 15426] New: Running many copies of bonnie++ on different filesystems seems to deadlock in sync
Date: Wed, 03 Mar 2010 13:37:25 +0100 [thread overview]
Message-ID: <4B8E5805.30505@Calva.COM> (raw)
In-Reply-To: <20100303115015.GN5768@kernel.dk>
Jens Axboe wrote:
> Is IO still going on, or does it appear to be stuck? From the traces
> below, we have various procs caught in waiting for a request. So if
> things are totally stuck, it could be some race in there.
>
I see I/O happening on three or four of the disks.
Just a thought. What exactly is sync(2) supposed to do - block until
there are no more dirty pages, or block until all pages that were dirty
when the sync was done are clean? In other words is the problem simply
that pages are being dirtied faster than the sync is writing them out?
next prev parent reply other threads:[~2010-03-03 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15426-10286@http.bugzilla.kernel.org/>
2010-03-03 0:16 ` [Bugme-new] [Bug 15426] New: Running many copies of bonnie++ on different filesystems seems to deadlock in sync Andrew Morton
2010-03-03 12:09 ` John Hughes
2010-03-03 11:50 ` Jens Axboe
2010-03-03 12:37 ` John Hughes [this message]
2010-03-03 12:03 ` Jens Axboe
2010-03-03 12:45 ` John Hughes
2010-03-03 12:09 ` Jens Axboe
2010-03-03 14:42 ` Andre Noll
2010-03-04 14:55 ` John Hughes
2010-03-04 17:42 ` Andre Noll
2010-03-05 10:44 ` John Hughes
2010-03-03 18:33 ` John Hughes
2010-03-04 11:16 ` John Hughes
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=4B8E5805.30505@Calva.COM \
--to=john@calva.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@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.