From: Pascal Schmidt <der.eremit@email.de>
To: Frank Cusack <fcusack@fcusack.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does Linux sync(2) wait?
Date: Sun, 21 Mar 2004 16:30:53 +0100 [thread overview]
Message-ID: <E1B54ub-00004H-OC@localhost> (raw)
In-Reply-To: <1C8xa-5lk-5@gated-at.bofh.it>
On Sun, 21 Mar 2004 11:40:08 +0100, you wrote in linux.kernel:
> Looking at 2.4 and 2.6 sources, Linux does appear to wait before returning.
> I'm especially interested if NFS data is sent to the server. (I want to
> be able to take a stable snapshot of a netapp volume.)
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.
--
Ciao,
Pascal
next parent reply other threads:[~2004-03-21 15:31 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 ` Pascal Schmidt [this message]
2004-03-22 0:59 ` Does Linux sync(2) wait? Chris Wedgwood
2004-03-22 3:44 ` Chris Friesen
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=E1B54ub-00004H-OC@localhost \
--to=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