Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 3 Aug 2005 21:16:24 +1000
From:      Peter Jeremy <PeterJeremy@optushome.com.au>
To:        Jeremie Le Hen <jeremie@le-hen.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Hot-swap SATA and atacontrol
Message-ID:  <20050803111624.GA271@cirb503493.alcatel.com.au>
In-Reply-To: <20050803082939.GE45385@obiwan.tataz.chchile.org>
References:  <20050802152009.GA29643@mercury.m202.net> <008c01c59777$42db5520$0b02a8c0@justin> <790a9fff050802084439209f7e@mail.gmail.com> <20050802160045.GA61854@freebie.xs4all.nl> <20050803024341.GA92499@over-yonder.net> <20050803082939.GE45385@obiwan.tataz.chchile.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2005-Aug-03 10:29:39 +0200, Jeremie Le Hen wrote:
>More seriously, I don't see the point in using sync(8) three times
>consecutively, except that's an indirect method to wait for the disk
>buffers to be flushed before powering down.  Please, correct me if I'm
>wrong.

The response I've seen on the PUPS or TUHS mailing list when this was
asked is (roughly):  The time taken to type sync<cr> three times on
a KSR33 is a good match for the time it takes a PDP-11 to flush its
buffers to a RK05.

There is absolutely no point in typing sync before unmounting
filesystems or halting any modern Unix - they all flush their
buffers as part of the unmount or halt processing.  (And the
invention of of FS_UNCLEAN means that mount and fsck know whether
the filesystem was unmounted cleanly or not).

-- 
Peter Jeremy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050803111624.GA271>