From: random832@fastmail.us (random832@fastmail.us)
Subject: [TUHS] sync; sync; sync; halt (was: Re: Illumos ))
Date: Fri, 16 Jan 2015 08:39:06 -0500 [thread overview]
Message-ID: <1421415546.919096.214748125.23E789CE@webmail.messagingengine.com> (raw)
In-Reply-To: <m2lhl3w238.fsf_-_@athene.hamartun.priv.no>
On Fri, Jan 16, 2015, at 03:40, Tom Ivar Helbekkmo wrote:
> What this means is that the second sync, by waiting for its own
> superblock writes, will wait until all the inode and file data flushes
> scheduled by the first one have completed.
Everything I've read indicates that nothing in the sync call actually
waits on anything, and that it's actually just the time taken to type
the second and third command on a 110 baud terminal gives the first one
time to finish executing.
next prev parent reply other threads:[~2015-01-16 13:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 6:22 [TUHS] Illumos ) Larry McVoy
2014-12-31 9:28 ` Wesley Parish
2014-12-31 13:13 ` John Cowan
2014-12-31 17:42 ` Diomidis Spinellis
2014-12-31 20:32 ` Clem Cole
2014-12-31 20:36 ` Larry McVoy
2014-12-31 22:19 ` Jacob Ritorto
2014-12-31 22:42 ` Larry McVoy
2014-12-31 22:50 ` Larry McVoy
2015-01-01 1:17 ` Larry McVoy
2015-01-01 1:34 ` Erik E. Fair
2015-01-05 12:02 ` Tim Bradshaw
2015-01-05 17:04 ` Jacob Ritorto
2015-01-06 4:54 ` Andy Kosela
2015-01-06 11:10 ` Kurt H Maier
2015-01-06 15:37 ` Tim Bradshaw
2015-01-09 9:23 ` Jose R. Valverde
2015-01-06 21:58 ` Clem Cole
2015-01-06 22:02 ` [TUHS] pre-FSCK days Ronald Natalie
2015-01-07 1:53 ` [TUHS] Illumos ) Dave Horsfall
2015-01-07 16:26 ` Clem Cole
2015-01-07 18:32 ` scj
2015-01-16 8:40 ` [TUHS] sync; sync; sync; halt (was: Re: Illumos )) Tom Ivar Helbekkmo
2015-01-16 13:39 ` random832 [this message]
2015-01-16 14:14 ` Brantley Coile
2014-12-31 9:46 ` [TUHS] Illumos ) arnold
2015-01-16 12:33 [TUHS] sync; sync; sync; halt (was: Re: Illumos )) Noel Chiappa
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=1421415546.919096.214748125.23E789CE@webmail.messagingengine.com \
--to=random832@fastmail.us \
/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;
as well as URLs for NNTP newsgroup(s).