From: Anil kumar Subject: EXT3 data=ordered system crash Date: Wed, 18 Aug 2010 19:23:07 -0700 (PDT) Message-ID: <539621.95249.qm@web32406.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: linux-fsdevel@vger.kernel.org Return-path: Received: from web32406.mail.mud.yahoo.com ([68.142.207.199]:43988 "HELO web32406.mail.mud.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750944Ab0HSCXI (ORCPT ); Wed, 18 Aug 2010 22:23:08 -0400 Sender: linux-fsdevel-owner@vger.kernel.org List-ID: As I understand by default EXT3 uses "data=ordered" journalling mode. In this case, 1)the Data is written to the disk 2)MetaData is written to the journal 3)Transaction complete With the above being the case, is there a possibility that if system crashes there will be filesystem inconsistency. My understanding is that it should not as Data is first written to the disk and if it fails(or incompletes) then there is record of it anyway in the journal and if system crashes during writing MetaData to the journal it should be okay as actual Data is already in the Disk.