From owner-freebsd-questions Wed Aug 13 21:37:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA21974 for questions-outgoing; Wed, 13 Aug 1997 21:37:42 -0700 (PDT) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA21960 for ; Wed, 13 Aug 1997 21:37:33 -0700 (PDT) Received: from gravel.sentex.ca (gravel.sentex.ca [205.211.165.210]) by granite.sentex.net (8.8.6/8.6.9) with SMTP id AAA04790; Thu, 14 Aug 1997 00:48:09 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: agent47@baldcom.net (Ken McKittrick) Cc: freebsd-questions@FreeBSD.ORG Subject: Re: mount -o asynch = better performance ??????? Date: Thu, 14 Aug 1997 04:35:22 GMT Message-ID: <33f2899b.95335755@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 13 Aug 1997 23:11:38 +0100, in sentex.lists.freebsd.questions you wrote: >How reliable is a file system if it's mounted asynch really???? I think its more of a question of how reliable is everything else. i.e. do you have a UPS in case of power loss, are there any apps you are running that would crash the machine for whatever reason. Async just means that there is more data at any given time in memory that is waiting to be written out. Running async lets the OS write are more convienient times. A good example is do a config with /usr mounted sync, and then async. You will see quite a difference in the time it takes. I have my newsspool mounted async, which is a pretty write intensive setup as you can imagine, and I have not had any problems to date (knock on wood). But again, its not that write behind caching is dangerous, its just dangerous if you have a crash. ---Mike