From owner-freebsd-fs Wed Mar 13 4: 8:18 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx7.mail.ru (mx7.mail.ru [194.67.57.17]) by hub.freebsd.org (Postfix) with ESMTP id 77A1537B416 for ; Wed, 13 Mar 2002 04:08:15 -0800 (PST) Received: from f9.int ([10.0.0.77] helo=f9.mail.ru) by mx7.mail.ru with esmtp (Exim MX.7) id 16l7YE-000K4I-00 for freebsd-fs@freebsd.org; Wed, 13 Mar 2002 15:08:14 +0300 Received: from mail by f9.mail.ru with local (Exim FE.9) id 16l7YD-0001FG-00 for freebsd-fs@FreeBSD.org; Wed, 13 Mar 2002 15:08:13 +0300 Received: from [144.16.67.8] by eng.mail.ru with HTTP; Wed, 13 Mar 2002 15:08:13 +0300 From: "Parity Error" To: freebsd-fs@FreeBSD.org Cc: Subject: metadata update durability ordering/soft updates Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: 144.16.67.147 via proxy [144.16.67.8] Date: Wed, 13 Mar 2002 15:08:13 +0300 Reply-To: "Parity Error" Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org with soft-updates metadata updates are delayed write. I am wondering if, say there are two independent structural changes, one after another, and then a crash happens. Is there a possibility that the latter structural change got written to disk before the former due to some memory replacement policy ? could this affect the correctness of some applications ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message