From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Filesystem bug? "sync" hangs...
Date: Sat, 07 Jul 2001 10:58:35 -0400 [thread overview]
Message-ID: <3B47239B.69E72F18@mandrakesoft.com> (raw)
Kernel 2.4.7-pre3 on alpha.
The initial phase of an RPM build is unpacking a tarball and applying
patches, which is a bunch of writes followed by a update of read/write
updates. A lot of write activity, basically. RPM build is running at
normal priority as a normal user.
In another xterm, su'd in a shell that is renice'd to -14, I run "sync"
during all this write activity. It hangs for 17 seconds before I get
impatient, stop counting, and suspend the RPM build process. sync
continues to block, not returning to the command prompt. I run dmesg
(generated read activity?), and sync finally returns.
The RPM build process continues unpacking/writing files without
appearing to slow in window 1 while sync blocks in window 2.
I have not seen this behavior before, but I do not recall trying 'sync'
specifically during heavy write activity before. This behavior is
reproducible.
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
reply other threads:[~2001-07-07 14:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B47239B.69E72F18@mandrakesoft.com \
--to=jgarzik@mandrakesoft.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.