From owner-freebsd-questions Mon Apr 17 4:25:19 2000 Delivered-To: freebsd-questions@freebsd.org Received: from tranquility.net (ppp-port3-32.tranquility.net [206.152.119.128]) by hub.freebsd.org (Postfix) with ESMTP id EE0E037B79A for ; Mon, 17 Apr 2000 04:25:07 -0700 (PDT) (envelope-from ishmael@tranquility.net) Received: from localhost (ishmael@localhost) by tranquility.net (8.9.3/8.9.3) with ESMTP id GAA06200; Mon, 17 Apr 2000 06:27:41 -0500 (CDT) (envelope-from ishmael@tranquility.net) Date: Mon, 17 Apr 2000 06:27:40 -0500 (CDT) From: Ishmael To: Rasmus Skaarup Cc: freebsd-questions@FreeBSD.ORG Subject: Re: disc io - sync and async In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > - Why does a simple 'mount' command tell me that both sync and async reads > > > and writes are being performed on me FreeBSD box? > > > > Because it looks cool? :) > > If async operations are performed anyhow, why don't we just mount the > drives async from the beginning. If FreeBSD chooses to mount drives in > sync or 'non-async' mode as you say, to increase integrity, and async > operations are performed anyway this doesn't help one bit. You still have > problems with integrity, and the drives will just be slower.. I think if i've read everything here in this thread, he meant that FreeBSD by default mounts drives 'non-async' which means all meta-data is written sync (meaning no caching), while all other data is writen async. This gives a combination of speed and integrity. Jeremy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message