From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Pascal Schmidt <der.eremit@email.de>,
Frank Cusack <fcusack@fcusack.com>,
linux-kernel@vger.kernel.org
Subject: Re: Does Linux sync(2) wait?
Date: Sun, 21 Mar 2004 22:44:29 -0500 [thread overview]
Message-ID: <405E611D.10008@nortelnetworks.com> (raw)
In-Reply-To: 20040322005953.GA12237@dingdong.cryptoapps.com
Chris Wedgwood wrote:
> On Sun, Mar 21, 2004 at 04:30:53PM +0100, Pascal Schmidt wrote:
>
>
>>No idea about NFS, but sync(1) does wait. When I push 500M out to my
>>MO drive, the cp operation returns fairly quickly because I usually
>>have more than 500M free memory. Then I run sync(1), which takes
>>about 20 minutes before it returns.
>>
>
> 20 minutes?!
He did say it was a magneto-optical drive.
Chris
next prev parent reply other threads:[~2004-03-22 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1C8xa-5lk-5@gated-at.bofh.it>
2004-03-21 15:30 ` Does Linux sync(2) wait? Pascal Schmidt
2004-03-22 0:59 ` Chris Wedgwood
2004-03-22 3:44 ` Chris Friesen [this message]
2004-03-22 12:08 ` Stefan Smietanowski
2004-03-22 14:27 ` Pascal Schmidt
2004-03-21 10:31 Frank Cusack
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=405E611D.10008@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=cw@f00f.org \
--cc=der.eremit@email.de \
--cc=fcusack@fcusack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox