From owner-freebsd-questions Wed Sep 22 8:21:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hermes.axis.de (hermes.axis.de [194.163.241.7]) by hub.freebsd.org (Postfix) with SMTP id 658D514CC3 for ; Wed, 22 Sep 1999 08:21:11 -0700 (PDT) (envelope-from maret@atrada.de) Received: from erlangen01.axis.de by hermes.axis.de via smtpd (for hub.FreeBSD.ORG [204.216.27.18]) with SMTP; 22 Sep 1999 15:21:13 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D23B9@erlangen01.axis.de> From: Alexander Maret To: "'freebsd-questions@freebsd.org'" Subject: softupdates: do I understand this correctly? Date: Wed, 22 Sep 1999 17:21:31 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've read the abstract about SoftUpdates but as my english is not that good I'm not sure if I understood everything correctly: Here is my current view of this topic: synchronous mode: doing a write operation in this mode causes the system to write all dependenies and then write the data to disk. The system waits for every command to be completed. Therefor this mode is slow but safe. asynchronous mode: the system starts every command (i.e. write dependencies, write data) and doesn't wait for the command beeing completed. Because of data being cashed this mode is not very safe. softupdates mode: the system cashes data and tracks dependencies to write cashed data (including dependencies) afterwards in one go (=delayed write). advantage of softupdates: - in case of a crash it is more likely that every data is already been written to disk because the system writes data in one go and doesn't have to wait i.e. for a program output while there is an open file. Can anybody confirm this or do I have a completly wrong view of this topic. Please comment my thoughts. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message