ext3.txt 6.3 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4

Ext3 Filesystem
===============

5 6
Ext3 was originally released in September 1999. Written by Stephen Tweedie
for the 2.2 branch, and ported to 2.4 kernels by Peter Braam, Andreas Dilger,
L
Linus Torvalds 已提交
7 8
Andrew Morton, Alexander Viro, Ted Ts'o and Stephen Tweedie.

9
Ext3 is the ext2 filesystem enhanced with journalling capabilities.
L
Linus Torvalds 已提交
10 11 12 13 14 15 16

Options
=======

When mounting an ext3 filesystem, the following option are accepted:
(*) == default

17 18
journal=update		Update the ext3 file system's journal to the current
			format.
L
Linus Torvalds 已提交
19

20 21 22
journal=inum		When a journal already exists, this option is ignored.
			Otherwise, it specifies the number of the inode which
			will represent the ext3 file system's journal file.
L
Linus Torvalds 已提交
23

24
journal_dev=devnum	When the external journal device's major/minor numbers
25 26 27 28
			have changed, this option allows the user to specify
			the new journal location.  The journal device is
			identified through its new major/minor numbers encoded
			in devnum.
29

L
Linus Torvalds 已提交
30 31
noload			Don't load the journal on mounting.

32 33
data=journal		All data are committed into the journal prior to being
			written into the main file system.
L
Linus Torvalds 已提交
34 35

data=ordered	(*)	All data are forced directly out to the main file
36 37
			system prior to its metadata being committed to the
			journal.
L
Linus Torvalds 已提交
38

39 40 41
data=writeback		Data ordering is not preserved, data may be written
			into the main file system after its metadata has been
			committed to the journal.
L
Linus Torvalds 已提交
42 43 44

commit=nrsec	(*)	Ext3 can be told to sync all its data and metadata
			every 'nrsec' seconds. The default value is 5 seconds.
45 46 47 48 49 50 51
			This means that if you lose your power, you will lose
			as much as the latest 5 seconds of work (your
			filesystem will not be damaged though, thanks to the
			journaling).  This default value (or any low value)
			will hurt performance, but it's good for data-safety.
			Setting it to 0 will have the same effect as leaving
			it at the default (5 seconds).
L
Linus Torvalds 已提交
52 53 54
			Setting it to very large values will improve
			performance.

55 56
barrier=1		This enables/disables barriers.  barrier=0 disables
			it, barrier=1 enables it.
L
Linus Torvalds 已提交
57

58 59
orlov		(*)	This enables the new Orlov block allocator. It is
			enabled by default.
L
Linus Torvalds 已提交
60

61 62 63 64
oldalloc		This disables the Orlov block allocator and enables
			the old block allocator.  Orlov should have better
			performance - we'd like to get some feedback if it's
			the contrary for you.
L
Linus Torvalds 已提交
65

66 67 68 69 70
user_xattr		Enables Extended User Attributes.  Additionally, you
			need to have extended attribute support enabled in the
			kernel configuration (CONFIG_EXT3_FS_XATTR).  See the
			attr(5) manual page and http://acl.bestbits.at/ to
			learn more about extended attributes.
71 72 73

nouser_xattr		Disables Extended User Attributes.

74 75 76 77 78
acl			Enables POSIX Access Control Lists support.
			Additionally, you need to have ACL support enabled in
			the kernel configuration (CONFIG_EXT3_FS_POSIX_ACL).
			See the acl(5) manual page and http://acl.bestbits.at/
			for more information.
L
Linus Torvalds 已提交
79

80 81
noacl			This option disables POSIX Access Control List
			support.
L
Linus Torvalds 已提交
82 83 84 85 86 87 88 89 90 91 92

reservation

noreservation

resize=

bsddf 		(*)	Make 'df' act like BSD.
minixdf			Make 'df' act like Minix.

check=none		Don't do extra checking of bitmaps on mount.
93
nocheck
L
Linus Torvalds 已提交
94 95 96 97 98 99 100 101

debug			Extra debugging information is sent to syslog.

errors=remount-ro(*)	Remount the filesystem read-only on an error.
errors=continue		Keep going on a filesystem error.
errors=panic		Panic and halt the machine if an error occurs.

grpid			Give objects the same group ID as their creator.
102
bsdgroups
L
Linus Torvalds 已提交
103 104 105 106 107 108 109 110 111 112

nogrpid		(*)	New objects have the group ID of their creator.
sysvgroups

resgid=n		The group ID which may use the reserved blocks.

resuid=n		The user ID which may use the reserved blocks.

sb=n			Use alternate superblock at this location.

113 114
quota
noquota
L
Linus Torvalds 已提交
115 116 117 118 119 120
grpquota
usrquota


Specification
=============
121 122 123
Ext3 shares all disk implementation with the ext2 filesystem, and adds
transactions capabilities to ext2.  Journaling is done by the Journaling Block
Device layer.
L
Linus Torvalds 已提交
124 125 126

Journaling Block Device layer
-----------------------------
127 128 129 130 131 132
The Journaling Block Device layer (JBD) isn't ext3 specific.  It was design to
add journaling capabilities on a block device.  The ext3 filesystem code will
inform the JBD of modifications it is performing (called a transaction).  The
journal supports the transactions start and stop, and in case of crash, the
journal can replayed the transactions to put the partition back in a
consistent state fast.
L
Linus Torvalds 已提交
133

134 135
Handles represent a single atomic update to a filesystem.  JBD can handle an
external journal on a block device.
L
Linus Torvalds 已提交
136 137 138

Data Mode
---------
139
There are 3 different data modes:
L
Linus Torvalds 已提交
140 141

* writeback mode
142 143 144 145 146
In data=writeback mode, ext3 does not journal data at all.  This mode provides
a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
mode - metadata journaling.  A crash+recovery can cause incorrect data to
appear in files which were written shortly before the crash.  This mode will
typically provide the best ext3 performance.
L
Linus Torvalds 已提交
147 148

* ordered mode
149 150 151 152 153
In data=ordered mode, ext3 only officially journals metadata, but it logically
groups metadata and data blocks into a single unit called a transaction.  When
it's time to write the new metadata out to disk, the associated data blocks
are written first.  In general, this mode performs slightly slower than
writeback but significantly faster than journal mode.
L
Linus Torvalds 已提交
154 155

* journal mode
156 157 158 159 160 161
data=journal mode provides full data and metadata journaling.  All new data is
written to the journal first, and then to its final location.
In the event of a crash, the journal can be replayed, bringing both data and
metadata into a consistent state.  This mode is the slowest except when data
needs to be read from and written to disk at the same time where it
outperforms all others modes.
L
Linus Torvalds 已提交
162 163 164 165 166

Compatibility
-------------

Ext2 partitions can be easily convert to ext3, with `tune2fs -j <dev>`.
167 168 169
Ext3 is fully compatible with Ext2.  Ext3 partitions can easily be mounted as
Ext2.

L
Linus Torvalds 已提交
170 171 172

External Tools
==============
173 174 175 176 177
See manual pages to learn more.

tune2fs: 	create a ext3 journal on a ext2 partition with the -j flag.
mke2fs: 	create a ext3 partition with the -j flag.
debugfs: 	ext2 and ext3 file system debugger.
L
Linus Torvalds 已提交
178 179 180 181 182


References
==========

183 184
kernel source:	<file:fs/ext3/>
		<file:fs/jbd/>
L
Linus Torvalds 已提交
185

186
programs: 	http://e2fsprogs.sourceforge.net/
L
Linus Torvalds 已提交
187

188
useful links:	http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html
L
Linus Torvalds 已提交
189 190
		http://www-106.ibm.com/developerworks/linux/library/l-fs7/
		http://www-106.ibm.com/developerworks/linux/library/l-fs8/