From: Stefan Smietanowski <stesmi@stesmi.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Chris Wedgwood <cw@f00f.org>,
Pascal Schmidt <der.eremit@email.de>,
Frank Cusack <fcusack@fcusack.com>,
linux-kernel@vger.kernel.org
Subject: Re: Does Linux sync(2) wait?
Date: Mon, 22 Mar 2004 13:08:53 +0100 [thread overview]
Message-ID: <405ED755.2070301@stesmi.com> (raw)
In-Reply-To: <405E611D.10008@nortelnetworks.com>
Hi.
>>> 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.
That's 400KiB/s you know - pretty slow.
// Stefan
next prev parent reply other threads:[~2004-03-22 12:09 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
2004-03-22 12:08 ` Stefan Smietanowski [this message]
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=405ED755.2070301@stesmi.com \
--to=stesmi@stesmi.com \
--cc=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 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.