blob: 919a3293aaa4249f81f0d907d9867d6d80f9a135 [file] [log] [blame]
Dave Kleikampfc513a32006-10-11 01:21:25 -07001
2Ext4 Filesystem
3===============
4
Masanari Iidac9f3f2d2013-07-18 01:29:12 +09005Ext4 is an advanced level of the ext3 filesystem which incorporates
Diego Calleja22359f52008-10-17 09:15:14 -04006scalability and reliability enhancements for supporting large filesystems
7(64 bit) in keeping with increasing disk capacities and state-of-the-art
8feature requirements.
Dave Kleikampfc513a32006-10-11 01:21:25 -07009
Diego Calleja22359f52008-10-17 09:15:14 -040010Mailing list: linux-ext4@vger.kernel.org
11Web site: http://ext4.wiki.kernel.org
Dave Kleikampfc513a32006-10-11 01:21:25 -070012
13
141. Quick usage instructions:
15===========================
16
Diego Calleja22359f52008-10-17 09:15:14 -040017Note: More extensive information for getting started with ext4 can be
18 found at the ext4 wiki site at the URL:
19 http://ext4.wiki.kernel.org/index.php/Ext4_Howto
20
Jose R. Santos93e32702008-07-11 19:27:31 -040021 - Compile and install the latest version of e2fsprogs (as of this
Diego Calleja22359f52008-10-17 09:15:14 -040022 writing version 1.41.3) from:
Jose R. Santos93e32702008-07-11 19:27:31 -040023
24 http://sourceforge.net/project/showfiles.php?group_id=2406
25
26 or
27
Dave Kleikampfc513a32006-10-11 01:21:25 -070028 ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/
29
Jose R. Santos93e32702008-07-11 19:27:31 -040030 or grab the latest git repository from:
Dave Kleikampfc513a32006-10-11 01:21:25 -070031
Jose R. Santos93e32702008-07-11 19:27:31 -040032 git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
Dave Kleikampfc513a32006-10-11 01:21:25 -070033
Theodore Ts'o45373982008-07-27 19:59:21 -040034 - Note that it is highly important to install the mke2fs.conf file
35 that comes with the e2fsprogs 1.41.x sources in /etc/mke2fs.conf. If
36 you have edited the /etc/mke2fs.conf file installed on your system,
37 you will need to merge your changes with the version from e2fsprogs
38 1.41.x.
39
Theodore Ts'o03010a32008-10-10 20:02:48 -040040 - Create a new filesystem using the ext4 filesystem type:
Dave Kleikampfc513a32006-10-11 01:21:25 -070041
Theodore Ts'o03010a32008-10-10 20:02:48 -040042 # mke2fs -t ext4 /dev/hda1
Dave Kleikampfc513a32006-10-11 01:21:25 -070043
Diego Calleja22359f52008-10-17 09:15:14 -040044 Or to configure an existing ext3 filesystem to support extents:
Dave Kleikampfc513a32006-10-11 01:21:25 -070045
Diego Calleja22359f52008-10-17 09:15:14 -040046 # tune2fs -O extents /dev/hda1
Jose R. Santos93e32702008-07-11 19:27:31 -040047
48 If the filesystem was created with 128 byte inodes, it can be
49 converted to use 256 byte for greater efficiency via:
50
51 # tune2fs -I 256 /dev/hda1
52
Theodore Ts'o03010a32008-10-10 20:02:48 -040053 (Note: we currently do not have tools to convert an ext4
Jose R. Santos93e32702008-07-11 19:27:31 -040054 filesystem back to ext3; so please do not do try this on production
55 filesystems.)
56
57 - Mounting:
58
Theodore Ts'o03010a32008-10-10 20:02:48 -040059 # mount -t ext4 /dev/hda1 /wherever
Dave Kleikampfc513a32006-10-11 01:21:25 -070060
Theodore Ts'o8e1a4852009-01-06 14:53:06 -050061 - When comparing performance with other filesystems, it's always
62 important to try multiple workloads; very often a subtle change in a
63 workload parameter can completely change the ranking of which
64 filesystems do well compared to others. When comparing versus ext3,
65 note that ext4 enables write barriers by default, while ext3 does
66 not enable write barriers by default. So it is useful to use
67 explicitly specify whether barriers are enabled or not when via the
68 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
69 for a fair comparison. When tuning ext3 for best benchmark numbers,
70 it is often worthwhile to try changing the data journaling mode; '-o
Lukas Czernerad434012011-06-07 12:27:05 +020071 data=writeback' can be faster for some workloads. (Note however that
72 running mounted with data=writeback can potentially leave stale data
73 exposed in recently written files in case of an unclean shutdown,
74 which could be a security exposure in some situations.) Configuring
75 the filesystem with a large journal can also be helpful for
76 metadata-intensive workloads.
Dave Kleikampfc513a32006-10-11 01:21:25 -070077
782. Features
79===========
80
812.1 Currently available
82
Jose R. Santos93e32702008-07-11 19:27:31 -040083* ability to use filesystems > 16TB (e2fsprogs support not available yet)
Dave Kleikampfc513a32006-10-11 01:21:25 -070084* extent format reduces metadata overhead (RAM, IO for access, transactions)
85* extent format more robust in face of on-disk corruption due to magics,
Theodore Ts'o8e1a4852009-01-06 14:53:06 -050086* internal redundancy in tree
Mingming Cao49f14872008-07-11 19:27:31 -040087* improved file allocation (multi-block alloc)
Theodore Ts'o722bde62009-02-23 00:51:57 -050088* lift 32000 subdirectory limit imposed by i_links_count[1]
Jose R. Santos93e32702008-07-11 19:27:31 -040089* nsec timestamps for mtime, atime, ctime, create time
90* inode version field on disk (NFSv4, Lustre)
91* reduced e2fsck time via uninit_bg feature
92* journal checksumming for robustness, performance
93* persistent file preallocation (e.g for streaming media, databases)
94* ability to pack bitmaps and inode tables into larger virtual groups via the
95 flex_bg feature
96* large file support
97* Inode allocation using large virtual block groups via flex_bg
Mingming Cao49f14872008-07-11 19:27:31 -040098* delayed allocation
99* large block (up to pagesize) support
Lucas De Marchi25985ed2011-03-30 22:57:33 -0300100* efficient new ordered mode in JBD2 and ext4(avoid using buffer head to force
Mingming Cao49f14872008-07-11 19:27:31 -0400101 the ordering)
Dave Kleikampfc513a32006-10-11 01:21:25 -0700102
Theodore Ts'o722bde62009-02-23 00:51:57 -0500103[1] Filesystems with a block size of 1k may see a limit imposed by the
104directory hash tree having a maximum depth of two.
105
Dave Kleikampfc513a32006-10-11 01:21:25 -07001062.2 Candidate features for future inclusion
107
Jose R. Santos93e32702008-07-11 19:27:31 -0400108* Online defrag (patches available but not well tested)
Lucas De Marchi25985ed2011-03-30 22:57:33 -0300109* reduced mke2fs time via lazy itable initialization in conjunction with
Jose R. Santos93e32702008-07-11 19:27:31 -0400110 the uninit_bg feature (capability to do this is available in e2fsprogs
111 but a kernel thread to do lazy zeroing of unused inode table blocks
112 after filesystem is first mounted is required for safety)
Dave Kleikampfc513a32006-10-11 01:21:25 -0700113
Jose R. Santos93e32702008-07-11 19:27:31 -0400114There are several others under discussion, whether they all make it in is
115partly a function of how much time everyone has to work on them. Features like
116metadata checksumming have been discussed and planned for a bit but no patches
117exist yet so I'm not sure they're in the near-term roadmap.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700118
Jose R. Santos93e32702008-07-11 19:27:31 -0400119The big performance win will come with mballoc, delalloc and flex_bg
120grouping of bitmaps and inode tables. Some test results available here:
Dave Kleikampfc513a32006-10-11 01:21:25 -0700121
Diego Calleja22359f52008-10-17 09:15:14 -0400122 - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-write-2.6.27-rc1.html
123 - http://www.bullopensource.org/ext4/20080818-ffsb/ffsb-readwrite-2.6.27-rc1.html
Dave Kleikampfc513a32006-10-11 01:21:25 -0700124
1253. Options
126==========
127
128When mounting an ext4 filesystem, the following option are accepted:
129(*) == default
130
Theodore Ts'o8e1a4852009-01-06 14:53:06 -0500131ro Mount filesystem read only. Note that ext4 will
132 replay the journal (and thus write to the
133 partition) even when mounted "read only". The
134 mount options "ro,noload" can be used to prevent
135 writes to the filesystem.
136
Linus Torvaldsd4da6c92009-11-02 10:15:27 -0800137journal_checksum Enable checksumming of the journal transactions.
138 This will allow the recovery code in e2fsck and the
139 kernel to detect corruption in the kernel. It is a
140 compatible change and will be ignored by older kernels.
141
Girish Shilamkar818d2762008-01-28 23:58:27 -0500142journal_async_commit Commit block can be written to disk without waiting
143 for descriptor blocks. If enabled older kernels cannot
Linus Torvaldsd4da6c92009-11-02 10:15:27 -0800144 mount the device. This will enable 'journal_checksum'
145 internally.
Girish Shilamkar818d2762008-01-28 23:58:27 -0500146
Eric Sandeenad4eec62013-08-28 19:05:07 -0400147journal_path=path
Dave Kleikampfc513a32006-10-11 01:21:25 -0700148journal_dev=devnum When the external journal device's major/minor numbers
Eric Sandeenad4eec62013-08-28 19:05:07 -0400149 have changed, these options allow the user to specify
Dave Kleikampfc513a32006-10-11 01:21:25 -0700150 the new journal location. The journal device is
Eric Sandeenad4eec62013-08-28 19:05:07 -0400151 identified through either its new major/minor numbers
152 encoded in devnum, or via a path to the device.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700153
Eric Sandeene3bb52a2009-11-19 14:28:50 -0500154norecovery Don't load the journal on mounting. Note that
155noload if the filesystem was not unmounted cleanly,
Theodore Ts'o8e1a4852009-01-06 14:53:06 -0500156 skipping the journal replay will lead to the
157 filesystem containing inconsistencies that can
158 lead to any number of problems.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700159
160data=journal All data are committed into the journal prior to being
Theodore Ts'o56889782011-09-03 18:22:38 -0400161 written into the main file system. Enabling
162 this mode will disable delayed allocation and
163 O_DIRECT support.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700164
165data=ordered (*) All data are forced directly out to the main file
166 system prior to its metadata being committed to the
167 journal.
168
169data=writeback Data ordering is not preserved, data may be written
170 into the main file system after its metadata has been
171 committed to the journal.
172
173commit=nrsec (*) Ext4 can be told to sync all its data and metadata
174 every 'nrsec' seconds. The default value is 5 seconds.
175 This means that if you lose your power, you will lose
176 as much as the latest 5 seconds of work (your
177 filesystem will not be damaged though, thanks to the
178 journaling). This default value (or any low value)
179 will hurt performance, but it's good for data-safety.
180 Setting it to 0 will have the same effect as leaving
181 it at the default (5 seconds).
182 Setting it to very large values will improve
183 performance.
184
Eric Sandeen571640c2008-05-26 12:29:46 -0400185barrier=<0|1(*)> This enables/disables the use of write barriers in
Theodore Ts'o06705bf2009-03-28 10:59:57 -0400186barrier(*) the jbd code. barrier=0 disables, barrier=1 enables.
187nobarrier This also requires an IO stack which can support
Eric Sandeen571640c2008-05-26 12:29:46 -0400188 barriers, and if jbd gets an error on a barrier
189 write, it will disable again with a warning.
190 Write barriers enforce proper on-disk ordering
191 of journal commits, making volatile disk write caches
192 safe to use, at some performance penalty. If
193 your disks are battery-backed in one way or another,
194 disabling barriers may safely improve performance.
Theodore Ts'o06705bf2009-03-28 10:59:57 -0400195 The mount options "barrier" and "nobarrier" can
196 also be used to enable or disable barriers, for
197 consistency with other ext4 mount options.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700198
Fang Wenqi6d3b82f2009-12-24 17:51:42 -0500199inode_readahead_blks=n This tuning parameter controls the maximum
Theodore Ts'o240799c2008-10-09 23:53:47 -0400200 number of inode table blocks that ext4's inode
201 table readahead algorithm will pre-read into
202 the buffer cache. The default value is 32 blocks.
203
Tao Ma939da102012-12-10 16:30:43 -0500204nouser_xattr Disables Extended User Attributes. See the
205 attr(5) manual page and http://acl.bestbits.at/
206 for more information about extended attributes.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700207
208noacl This option disables POSIX Access Control List
Theodore Ts'oaf909a52011-10-08 14:01:08 -0400209 support. If ACL support is enabled in the kernel
210 configuration (CONFIG_EXT4_FS_POSIX_ACL), ACL is
211 enabled by default on mount. See the acl(5) manual
212 page and http://acl.bestbits.at/ for more information
213 about acl.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700214
Dave Kleikampfc513a32006-10-11 01:21:25 -0700215bsddf (*) Make 'df' act like BSD.
216minixdf Make 'df' act like Minix.
217
Dave Kleikampfc513a32006-10-11 01:21:25 -0700218debug Extra debugging information is sent to syslog.
219
Theodore Ts'o8a8a2052009-06-13 10:08:59 -0400220abort Simulate the effects of calling ext4_abort() for
221 debugging purposes. This is normally used while
222 remounting a filesystem which is already mounted.
223
Theodore Ts'o8e1a4852009-01-06 14:53:06 -0500224errors=remount-ro Remount the filesystem read-only on an error.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700225errors=continue Keep going on a filesystem error.
226errors=panic Panic and halt the machine if an error occurs.
Theodore Ts'o8e1a4852009-01-06 14:53:06 -0500227 (These mount options override the errors behavior
228 specified in the superblock, which can be configured
229 using tune2fs)
Dave Kleikampfc513a32006-10-11 01:21:25 -0700230
Hidehiro Kawai5bf56832008-10-10 22:12:43 -0400231data_err=ignore(*) Just print an error message if an error occurs
232 in a file data buffer in ordered mode.
233data_err=abort Abort the journal if an error occurs in a file
234 data buffer in ordered mode.
235
Dave Kleikampfc513a32006-10-11 01:21:25 -0700236grpid Give objects the same group ID as their creator.
237bsdgroups
238
239nogrpid (*) New objects have the group ID of their creator.
240sysvgroups
241
242resgid=n The group ID which may use the reserved blocks.
243
244resuid=n The user ID which may use the reserved blocks.
245
246sb=n Use alternate superblock at this location.
247
Jan Kara13588702009-09-18 12:22:29 -0400248quota These options are ignored by the filesystem. They
249noquota are used only by quota tools to recognize volumes
250grpquota where quota should be turned on. See documentation
251usrquota in the quota-tools package for more details
252 (http://sourceforge.net/projects/linuxquota).
253
254jqfmt=<quota type> These options tell filesystem details about quota
255usrjquota=<file> so that quota information can be properly updated
256grpjquota=<file> during journal replay. They replace the above
257 quota options. See documentation in the quota-tools
258 package for more details
259 (http://sourceforge.net/projects/linuxquota).
Dave Kleikampfc513a32006-10-11 01:21:25 -0700260
Alex Tomasc9de5602008-01-29 00:19:52 -0500261stripe=n Number of filesystem blocks that mballoc will try
262 to use for allocation size and alignment. For RAID5/6
263 systems this should be the number of data
264 disks * RAID chunk size in file system blocks.
Jan Kara83653882009-09-29 15:59:34 -0400265
266delalloc (*) Defer block allocation until just before ext4
267 writes out the block(s) in question. This
268 allows ext4 to better allocation decisions
269 more efficiently.
270nodelalloc Disable delayed allocation. Blocks are allocated
271 when the data is copied from userspace to the
272 page cache, either via the write(2) system call
273 or when an mmap'ed page which was previously
274 unallocated is written for the first time.
Theodore Ts'o240799c2008-10-09 23:53:47 -0400275
Theodore Ts'o30773842009-01-03 20:27:38 -0500276max_batch_time=usec Maximum amount of time ext4 should wait for
277 additional filesystem operations to be batch
278 together with a synchronous write operation.
279 Since a synchronous write operation is going to
280 force a commit and then a wait for the I/O
281 complete, it doesn't cost much, and can be a
282 huge throughput win, we wait for a small amount
283 of time to see if any other transactions can
284 piggyback on the synchronous write. The
285 algorithm used is designed to automatically tune
286 for the speed of the disk, by measuring the
287 amount of time (on average) that it takes to
288 finish committing a transaction. Call this time
289 the "commit time". If the time that the
Matt LaPlante19f59462009-04-27 15:06:31 +0200290 transaction has been running is less than the
Theodore Ts'o30773842009-01-03 20:27:38 -0500291 commit time, ext4 will try sleeping for the
292 commit time to see if other operations will join
293 the transaction. The commit time is capped by
294 the max_batch_time, which defaults to 15000us
295 (15ms). This optimization can be turned off
296 entirely by setting max_batch_time to 0.
297
298min_batch_time=usec This parameter sets the commit time (as
299 described above) to be at least min_batch_time.
300 It defaults to zero microseconds. Increasing
301 this parameter may improve the throughput of
302 multi-threaded, synchronous workloads on very
303 fast disks, at the cost of increasing latency.
304
Theodore Ts'ob3881f72009-01-05 22:46:26 -0500305journal_ioprio=prio The I/O priority (from 0 to 7, where 0 is the
Masanari Iida40e47122012-03-04 23:16:11 +0900306 highest priority) which should be used for I/O
Theodore Ts'ob3881f72009-01-05 22:46:26 -0500307 operations submitted by kjournald2 during a
308 commit operation. This defaults to 3, which is
309 a slightly higher priority than the default I/O
310 priority.
311
Theodore Ts'o06705bf2009-03-28 10:59:57 -0400312auto_da_alloc(*) Many broken applications don't use fsync() when
313noauto_da_alloc replacing existing files via patterns such as
314 fd = open("foo.new")/write(fd,..)/close(fd)/
315 rename("foo.new", "foo"), or worse yet,
316 fd = open("foo", O_TRUNC)/write(fd,..)/close(fd).
317 If auto_da_alloc is enabled, ext4 will detect
318 the replace-via-rename and replace-via-truncate
319 patterns and force that any delayed allocation
320 blocks are allocated such that at the next
321 journal commit, in the default data=ordered
322 mode, the data blocks of the new file are forced
323 to disk before the rename() operation is
Matt LaPlante19f59462009-04-27 15:06:31 +0200324 committed. This provides roughly the same level
Theodore Ts'o06705bf2009-03-28 10:59:57 -0400325 of guarantees as ext3, and avoids the
326 "zero-length" problem that can happen when a
327 system crashes before the delayed allocation
328 blocks are forced to disk.
329
Lukas Czernerbfff6872010-10-27 21:30:05 -0400330noinit_itable Do not initialize any uninitialized inode table
331 blocks in the background. This feature may be
332 used by installation CD's so that the install
333 process can complete as quickly as possible; the
334 inode table initialization process would then be
335 deferred until the next time the file system
336 is unmounted.
337
338init_itable=n The lazy itable init code will wait n times the
339 number of milliseconds it took to zero out the
340 previous block group's inode table. This
Masanari Iida40e47122012-03-04 23:16:11 +0900341 minimizes the impact on the system performance
Lukas Czernerbfff6872010-10-27 21:30:05 -0400342 while file system's inode table is being initialized.
343
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500344discard Controls whether ext4 should issue discard/TRIM
Eric Sandeen5328e632009-11-19 14:25:42 -0500345nodiscard(*) commands to the underlying block device when
346 blocks are freed. This is useful for SSD devices
347 and sparse/thinly-provisioned LUNs, but it is off
348 by default until sufficient testing has been done.
349
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500350nouid32 Disables 32-bit UIDs and GIDs. This is for
351 interoperability with older kernels which only
352 store and expect 16-bit values.
353
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500354block_validity This options allows to enables/disables the in-kernel
355noblock_validity facility for tracking filesystem metadata blocks
356 within internal data structures. This allows multi-
357 block allocator and other routines to quickly locate
358 extents which might overlap with filesystem metadata
359 blocks. This option is intended for debugging
360 purposes and since it negatively affects the
361 performance, it is off by default.
362
363dioread_lock Controls whether or not ext4 should use the DIO read
364dioread_nolock locking. If the dioread_nolock option is specified
365 ext4 will allocate uninitialized extent before buffer
366 write and convert the extent to initialized after IO
367 completes. This approach allows ext4 code to avoid
368 using inode mutex, which improves scalability on high
Lukas Czernerad434012011-06-07 12:27:05 +0200369 speed storages. However this does not work with
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500370 data journaling and dioread_nolock option will be
371 ignored with kernel warning. Note that dioread_nolock
372 code path is only used for extent-based files.
373 Because of the restrictions this options comprises
374 it is off by default (e.g. dioread_lock).
375
Theodore Ts'odf981d02012-08-17 09:48:17 -0400376max_dir_size_kb=n This limits the size of directories so that any
377 attempt to expand them beyond the specified
378 limit in kilobytes will cause an ENOSPC error.
379 This is useful in memory constrained
380 environments, where a very large directory can
381 cause severe performance problems or even
382 provoke the Out Of Memory killer. (For example,
383 if there is only 512mb memory available, a 176mb
384 directory may seriously cramp the system's style.)
385
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500386i_version Enable 64-bit inode version support. This option is
387 off by default.
388
Dave Kleikampfc513a32006-10-11 01:21:25 -0700389Data Mode
Jose R. Santos93e32702008-07-11 19:27:31 -0400390=========
Dave Kleikampfc513a32006-10-11 01:21:25 -0700391There are 3 different data modes:
392
393* writeback mode
394In data=writeback mode, ext4 does not journal data at all. This mode provides
395a similar level of journaling as that of XFS, JFS, and ReiserFS in its default
396mode - metadata journaling. A crash+recovery can cause incorrect data to
397appear in files which were written shortly before the crash. This mode will
398typically provide the best ext4 performance.
399
400* ordered mode
401In data=ordered mode, ext4 only officially journals metadata, but it logically
Mingming Cao49f14872008-07-11 19:27:31 -0400402groups metadata information related to data changes with the data blocks into a
403single unit called a transaction. When it's time to write the new metadata
404out to disk, the associated data blocks are written first. In general,
405this mode performs slightly slower than writeback but significantly faster than journal mode.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700406
407* journal mode
408data=journal mode provides full data and metadata journaling. All new data is
409written to the journal first, and then to its final location.
410In the event of a crash, the journal can be replayed, bringing both data and
411metadata into a consistent state. This mode is the slowest except when data
412needs to be read from and written to disk at the same time where it
Theodore Ts'o56889782011-09-03 18:22:38 -0400413outperforms all others modes. Enabling this mode will disable delayed
414allocation and O_DIRECT support.
Dave Kleikampfc513a32006-10-11 01:21:25 -0700415
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500416/proc entries
417=============
418
419Information about mounted ext4 file systems can be found in
420/proc/fs/ext4. Each mounted filesystem will have a directory in
421/proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
422/proc/fs/ext4/dm-0). The files in each per-device directory are shown
423in table below.
424
425Files in /proc/fs/ext4/<devname>
426..............................................................................
427 File Content
428 mb_groups details of multiblock allocator buddy cache of free blocks
429..............................................................................
430
431/sys entries
432============
433
434Information about mounted ext4 file systems can be found in
435/sys/fs/ext4. Each mounted filesystem will have a directory in
436/sys/fs/ext4 based on its device name (i.e., /sys/fs/ext4/hdc or
437/sys/fs/ext4/dm-0). The files in each per-device directory are shown
438in table below.
439
440Files in /sys/fs/ext4/<devname>
441(see also Documentation/ABI/testing/sysfs-fs-ext4)
442..............................................................................
443 File Content
444
445 delayed_allocation_blocks This file is read-only and shows the number of
446 blocks that are dirty in the page cache, but
447 which do not have their location in the
448 filesystem allocated yet.
449
450 inode_goal Tuning parameter which (if non-zero) controls
451 the goal inode used by the inode allocator in
452 preference to all other allocation heuristics.
453 This is intended for debugging use only, and
454 should be 0 on production systems.
455
456 inode_readahead_blks Tuning parameter which controls the maximum
457 number of inode table blocks that ext4's inode
458 table readahead algorithm will pre-read into
459 the buffer cache
460
461 lifetime_write_kbytes This file is read-only and shows the number of
462 kilobytes of data that have been written to this
463 filesystem since it was created.
464
465 max_writeback_mb_bump The maximum number of megabytes the writeback
466 code will try to write out before move on to
467 another inode.
468
469 mb_group_prealloc The multiblock allocator will round up allocation
470 requests to a multiple of this tuning parameter if
471 the stripe size is not set in the ext4 superblock
472
473 mb_max_to_scan The maximum number of extents the multiblock
474 allocator will search to find the best extent
475
476 mb_min_to_scan The minimum number of extents the multiblock
477 allocator will search to find the best extent
478
479 mb_order2_req Tuning parameter which controls the minimum size
480 for requests (as a power of 2) where the buddy
481 cache is used
482
483 mb_stats Controls whether the multiblock allocator should
484 collect statistics, which are shown during the
485 unmount. 1 means to collect statistics, 0 means
486 not to collect statistics
487
488 mb_stream_req Files which have fewer blocks than this tunable
489 parameter will have their blocks allocated out
490 of a block group specific preallocation pool, so
491 that small files are packed closely together.
492 Each large file will have its blocks allocated
493 out of its own unique preallocation pool.
494
495 session_write_kbytes This file is read-only and shows the number of
496 kilobytes of data that have been written to this
497 filesystem since it was mounted.
Lukas Czerner27dd4382013-04-09 22:11:22 -0400498
499 reserved_clusters This is RW file and contains number of reserved
500 clusters in the file system which will be used
501 in the specific situations to avoid costly
502 zeroout, unexpected ENOSPC, or possible data
503 loss. The default is 2% or 4096 clusters,
504 whichever is smaller and this can be changed
505 however it can never exceed number of clusters
506 in the file system. If there is not enough space
507 for the reserved space when mounting the file
508 mount will _not_ fail.
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500509..............................................................................
510
511Ioctls
512======
513
514There is some Ext4 specific functionality which can be accessed by applications
515through the system call interfaces. The list of all Ext4 specific ioctls are
516shown in the table below.
517
518Table of Ext4 specific ioctls
519..............................................................................
520 Ioctl Description
521 EXT4_IOC_GETFLAGS Get additional attributes associated with inode.
522 The ioctl argument is an integer bitfield, with
523 bit values described in ext4.h. This ioctl is an
524 alias for FS_IOC_GETFLAGS.
525
526 EXT4_IOC_SETFLAGS Set additional attributes associated with inode.
527 The ioctl argument is an integer bitfield, with
528 bit values described in ext4.h. This ioctl is an
529 alias for FS_IOC_SETFLAGS.
530
531 EXT4_IOC_GETVERSION
532 EXT4_IOC_GETVERSION_OLD
533 Get the inode i_generation number stored for
534 each inode. The i_generation number is normally
535 changed only when new inode is created and it is
536 particularly useful for network filesystems. The
537 '_OLD' version of this ioctl is an alias for
538 FS_IOC_GETVERSION.
539
540 EXT4_IOC_SETVERSION
541 EXT4_IOC_SETVERSION_OLD
542 Set the inode i_generation number stored for
543 each inode. The '_OLD' version of this ioctl
544 is an alias for FS_IOC_SETVERSION.
545
546 EXT4_IOC_GROUP_EXTEND This ioctl has the same purpose as the resize
547 mount option. It allows to resize filesystem
548 to the end of the last existing block group,
549 further resize has to be done with resize2fs,
550 either online, or offline. The argument points
551 to the unsigned logn number representing the
552 filesystem new block count.
553
554 EXT4_IOC_MOVE_EXT Move the block extents from orig_fd (the one
555 this ioctl is pointing to) to the donor_fd (the
556 one specified in move_extent structure passed
557 as an argument to this ioctl). Then, exchange
558 inode metadata between orig_fd and donor_fd.
559 This is especially useful for online
560 defragmentation, because the allocator has the
561 opportunity to allocate moved blocks better,
562 ideally into one contiguous extent.
563
564 EXT4_IOC_GROUP_ADD Add a new group descriptor to an existing or
565 new group descriptor block. The new group
566 descriptor is described by ext4_new_group_input
567 structure, which is passed as an argument to
568 this ioctl. This is especially useful in
569 conjunction with EXT4_IOC_GROUP_EXTEND,
570 which allows online resize of the filesystem
571 to the end of the last existing block group.
572 Those two ioctls combined is used in userspace
573 online resize tool (e.g. resize2fs).
574
575 EXT4_IOC_MIGRATE This ioctl operates on the filesystem itself.
576 It converts (migrates) ext3 indirect block mapped
577 inode to ext4 extent mapped inode by walking
578 through indirect block mapping of the original
579 inode and converting contiguous block ranges
580 into ext4 extents of the temporary inode. Then,
581 inodes are swapped. This ioctl might help, when
582 migrating from ext3 to ext4 filesystem, however
583 suggestion is to create fresh ext4 filesystem
584 and copy data from the backup. Note, that
585 filesystem has to support extents for this ioctl
586 to work.
587
588 EXT4_IOC_ALLOC_DA_BLKS Force all of the delay allocated blocks to be
589 allocated to preserve application-expected ext3
590 behaviour. Note that this will also start
591 triggering a write of the data blocks, but this
592 behaviour may change in the future as it is
593 not necessary and has been done this way only
594 for sake of simplicity.
Yongqiang Yang19c52462012-01-04 17:09:44 -0500595
596 EXT4_IOC_RESIZE_FS Resize the filesystem to a new size. The number
597 of blocks of resized filesystem is passed in via
598 64 bit integer argument. The kernel allocates
599 bitmaps and inode table, the userspace tool thus
600 just passes the new number of blocks.
601
Dr. Tilmann Bubeck393d1d12013-04-08 12:54:05 -0400602EXT4_IOC_SWAP_BOOT Swap i_blocks and associated attributes
603 (like i_blocks, i_size, i_flags, ...) from
604 the specified inode with inode
605 EXT4_BOOT_LOADER_INO (#5). This is typically
606 used to store a boot loader in a secure part of
607 the filesystem, where it can't be changed by a
608 normal user by accident.
609 The data blocks of the previous boot loader
610 will be associated with the given inode.
611
Lukas Czerner6f9524e2011-02-21 20:16:21 -0500612..............................................................................
613
Dave Kleikampfc513a32006-10-11 01:21:25 -0700614References
615==========
616
617kernel source: <file:fs/ext4/>
618 <file:fs/jbd2/>
619
620programs: http://e2fsprogs.sourceforge.net/
Dave Kleikampfc513a32006-10-11 01:21:25 -0700621
622useful links: http://fedoraproject.org/wiki/ext3-devel
623 http://www.bullopensource.org/ext4/
Jose R. Santos93e32702008-07-11 19:27:31 -0400624 http://ext4.wiki.kernel.org/index.php/Main_Page
625 http://fedoraproject.org/wiki/Features/Ext4