Re: EXT3 data=ordered system crash

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed 18-08-10 19:23:07, Anil kumar wrote:
> 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.
  Yes. You can find what mode the filesystem is using by looking at
/proc/mounts. It is data=ordered by default but superblock flags can
influence this as well and for some time there was a kernel config option
so that we defaulted to data=writeback when no other mode was specified...

									Honza
-- 
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux