Skip to content

L
linux
Commit c0e3e040 authored by Darrick J. Wong's avatar Darrick J. Wong Committed by Theodore Ts'o
Browse files
Options

docs: make ext4 readme tables readable 

The tables in the ext4 readme are not particularly space efficient in
the text or html outputs, and they're totally broken in the pdf output.
Convert them into titled paragraphs so that they render more nicely.
Signed-off-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: default avatarTheodore Ts'o <tytso@mit.edu>
parent de7abd7b
Show whitespace changes
Inline Side-by-side
Showing with 391 additions and 430 deletions
Documentation/filesystems/ext4/ext4.rst
View file @ c0e3e040
...@@ -101,269 +101,256 @@ Options ...@@ -101,269 +101,256 @@ Options
When mounting an ext4 filesystem, the following option are accepted: When mounting an ext4 filesystem, the following option are accepted:
(*) == default (*) == default
======================= ======================================================= ro
Mount Option Description Mount filesystem read only. Note that ext4 will replay the journal (and
======================= ======================================================= thus write to the partition) even when mounted "read only". The mount
ro Mount filesystem read only. Note that ext4 will options "ro,noload" can be used to prevent writes to the filesystem.
replay the journal (and thus write to the
partition) even when mounted "read only". The journal_checksum
mount options "ro,noload" can be used to prevent Enable checksumming of the journal transactions. This will allow the
writes to the filesystem. recovery code in e2fsck and the kernel to detect corruption in the
kernel. It is a compatible change and will be ignored by older
journal_checksum Enable checksumming of the journal transactions. kernels.
This will allow the recovery code in e2fsck and the
kernel to detect corruption in the kernel. It is a journal_async_commit
compatible change and will be ignored by older kernels. Commit block can be written to disk without waiting for descriptor
blocks. If enabled older kernels cannot mount the device. This will
journal_async_commit Commit block can be written to disk without waiting enable 'journal_checksum' internally.
for descriptor blocks. If enabled older kernels cannot
mount the device. This will enable 'journal_checksum' journal_path=path, journal_dev=devnum
internally. When the external journal device's major/minor numbers have changed,
these options allow the user to specify the new journal location. The
journal_path=path journal device is identified through either its new major/minor numbers
journal_dev=devnum When the external journal device's major/minor numbers
have changed, these options allow the user to specify
the new journal location. The journal device is
identified through either its new major/minor numbers
encoded in devnum, or via a path to the device. encoded in devnum, or via a path to the device.
norecovery Don't load the journal on mounting. Note that norecovery, noload
noload if the filesystem was not unmounted cleanly, Don't load the journal on mounting. Note that if the filesystem was
skipping the journal replay will lead to the not unmounted cleanly, skipping the journal replay will lead to the
filesystem containing inconsistencies that can filesystem containing inconsistencies that can lead to any number of
lead to any number of problems. problems.
data=journal All data are committed into the journal prior to being data=journal
written into the main file system. Enabling All data are committed into the journal prior to being written into the
this mode will disable delayed allocation and main file system. Enabling this mode will disable delayed allocation
O_DIRECT support. and O_DIRECT support.
data=ordered (*) All data are forced directly out to the main file data=ordered (*)
system prior to its metadata being committed to the All data are forced directly out to the main file system prior to its
journal. metadata being committed to the journal.
data=writeback Data ordering is not preserved, data may be written data=writeback
into the main file system after its metadata has been Data ordering is not preserved, data may be written into the main file
committed to the journal. system after its metadata has been committed to the journal.
commit=nrsec (*) Ext4 can be told to sync all its data and metadata commit=nrsec (*)
every 'nrsec' seconds. The default value is 5 seconds. Ext4 can be told to sync all its data and metadata every 'nrsec'
This means that if you lose your power, you will lose seconds. The default value is 5 seconds. This means that if you lose
as much as the latest 5 seconds of work (your your power, you will lose as much as the latest 5 seconds of work (your
filesystem will not be damaged though, thanks to the filesystem will not be damaged though, thanks to the journaling). This
journaling). This default value (or any low value) default value (or any low value) will hurt performance, but it's good
will hurt performance, but it's good for data-safety. for data-safety. Setting it to 0 will have the same effect as leaving
Setting it to 0 will have the same effect as leaving it at the default (5 seconds). Setting it to very large values will
it at the default (5 seconds). improve performance.
Setting it to very large values will improve
performance. barrier=<0|1(*)>, barrier(*), nobarrier
This enables/disables the use of write barriers in the jbd code.
barrier=<0|1(*)> This enables/disables the use of write barriers in barrier=0 disables, barrier=1 enables. This also requires an IO stack
barrier(*) the jbd code. barrier=0 disables, barrier=1 enables. which can support barriers, and if jbd gets an error on a barrier
nobarrier This also requires an IO stack which can support write, it will disable again with a warning. Write barriers enforce
barriers, and if jbd gets an error on a barrier proper on-disk ordering of journal commits, making volatile disk write
write, it will disable again with a warning. caches safe to use, at some performance penalty. If your disks are
Write barriers enforce proper on-disk ordering battery-backed in one way or another, disabling barriers may safely
of journal commits, making volatile disk write caches improve performance. The mount options "barrier" and "nobarrier" can
safe to use, at some performance penalty. If also be used to enable or disable barriers, for consistency with other
your disks are battery-backed in one way or another, ext4 mount options.
disabling barriers may safely improve performance.
The mount options "barrier" and "nobarrier" can inode_readahead_blks=n
also be used to enable or disable barriers, for This tuning parameter controls the maximum number of inode table blocks
consistency with other ext4 mount options. that ext4's inode table readahead algorithm will pre-read into the
buffer cache. The default value is 32 blocks.
inode_readahead_blks=n This tuning parameter controls the maximum
number of inode table blocks that ext4's inode nouser_xattr
table readahead algorithm will pre-read into Disables Extended User Attributes. See the attr(5) manual page for
the buffer cache. The default value is 32 blocks. more information about extended attributes.
nouser_xattr Disables Extended User Attributes. See the noacl
attr(5) manual page for more information about This option disables POSIX Access Control List support. If ACL support
extended attributes. is enabled in the kernel configuration (CONFIG_EXT4_FS_POSIX_ACL), ACL
is enabled by default on mount. See the acl(5) manual page for more
noacl This option disables POSIX Access Control List information about acl.
support. If ACL support is enabled in the kernel
configuration (CONFIG_EXT4_FS_POSIX_ACL), ACL is bsddf (*)
enabled by default on mount. See the acl(5) manual Make 'df' act like BSD.
page for more information about acl.
minixdf
bsddf (*) Make 'df' act like BSD. Make 'df' act like Minix.
minixdf Make 'df' act like Minix.
debug
debug Extra debugging information is sent to syslog. Extra debugging information is sent to syslog.
abort Simulate the effects of calling ext4_abort() for abort
debugging purposes. This is normally used while Simulate the effects of calling ext4_abort() for debugging purposes.
remounting a filesystem which is already mounted. This is normally used while remounting a filesystem which is already
mounted.
errors=remount-ro Remount the filesystem read-only on an error.
errors=continue Keep going on a filesystem error. errors=remount-ro
errors=panic Panic and halt the machine if an error occurs. Remount the filesystem read-only on an error.
(These mount options override the errors behavior
specified in the superblock, which can be configured errors=continue
using tune2fs) Keep going on a filesystem error.
data_err=ignore(*) Just print an error message if an error occurs errors=panic
in a file data buffer in ordered mode. Panic and halt the machine if an error occurs. (These mount options
data_err=abort Abort the journal if an error occurs in a file override the errors behavior specified in the superblock, which can be
data buffer in ordered mode. configured using tune2fs)
grpid New objects have the group ID of their parent. data_err=ignore(*)
bsdgroups Just print an error message if an error occurs in a file data buffer in
ordered mode.
nogrpid (*) New objects have the group ID of their creator. data_err=abort
sysvgroups Abort the journal if an error occurs in a file data buffer in ordered
mode.
resgid=n The group ID which may use the reserved blocks.
grpid | bsdgroups
resuid=n The user ID which may use the reserved blocks. New objects have the group ID of their parent.
sb=n Use alternate superblock at this location. nogrpid (*) | sysvgroups
New objects have the group ID of their creator.
quota These options are ignored by the filesystem. They
noquota are used only by quota tools to recognize volumes resgid=n
grpquota where quota should be turned on. See documentation The group ID which may use the reserved blocks.
usrquota in the quota-tools package for more details
resuid=n
The user ID which may use the reserved blocks.
sb=
Use alternate superblock at this location.
quota, noquota, grpquota, usrquota
These options are ignored by the filesystem. They are used only by
quota tools to recognize volumes where quota should be turned on. See
documentation in the quota-tools package for more details
(http://sourceforge.net/projects/linuxquota). (http://sourceforge.net/projects/linuxquota).
jqfmt=<quota type> These options tell filesystem details about quota jqfmt=<quota type>, usrjquota=<file>, grpjquota=<file>
usrjquota=<file> so that quota information can be properly updated These options tell filesystem details about quota so that quota
grpjquota=<file> during journal replay. They replace the above information can be properly updated during journal replay. They replace
quota options. See documentation in the quota-tools the above quota options. See documentation in the quota-tools package
package for more details for more details (http://sourceforge.net/projects/linuxquota).
(http://sourceforge.net/projects/linuxquota).
stripe=n
stripe=n Number of filesystem blocks that mballoc will try Number of filesystem blocks that mballoc will try to use for allocation
to use for allocation size and alignment. For RAID5/6 size and alignment. For RAID5/6 systems this should be the number of
systems this should be the number of data data disks * RAID chunk size in file system blocks.
disks * RAID chunk size in file system blocks.
delalloc (*)
delalloc (*) Defer block allocation until just before ext4 Defer block allocation until just before ext4 writes out the block(s)
writes out the block(s) in question. This in question. This allows ext4 to better allocation decisions more
allows ext4 to better allocation decisions efficiently.
more efficiently.
nodelalloc Disable delayed allocation. Blocks are allocated nodelalloc
when the data is copied from userspace to the Disable delayed allocation. Blocks are allocated when the data is
page cache, either via the write(2) system call copied from userspace to the page cache, either via the write(2) system
or when an mmap'ed page which was previously call or when an mmap'ed page which was previously unallocated is
unallocated is written for the first time. written for the first time.
max_batch_time=usec Maximum amount of time ext4 should wait for max_batch_time=usec
additional filesystem operations to be batch Maximum amount of time ext4 should wait for additional filesystem
together with a synchronous write operation. operations to be batch together with a synchronous write operation.
Since a synchronous write operation is going to Since a synchronous write operation is going to force a commit and then
force a commit and then a wait for the I/O a wait for the I/O complete, it doesn't cost much, and can be a huge
complete, it doesn't cost much, and can be a throughput win, we wait for a small amount of time to see if any other
huge throughput win, we wait for a small amount transactions can piggyback on the synchronous write. The algorithm
of time to see if any other transactions can used is designed to automatically tune for the speed of the disk, by
piggyback on the synchronous write. The measuring the amount of time (on average) that it takes to finish
algorithm used is designed to automatically tune committing a transaction. Call this time the "commit time". If the
for the speed of the disk, by measuring the time that the transaction has been running is less than the commit
amount of time (on average) that it takes to time, ext4 will try sleeping for the commit time to see if other
finish committing a transaction. Call this time operations will join the transaction. The commit time is capped by
the "commit time". If the time that the the max_batch_time, which defaults to 15000us (15ms). This
transaction has been running is less than the optimization can be turned off entirely by setting max_batch_time to 0.
commit time, ext4 will try sleeping for the
commit time to see if other operations will join min_batch_time=usec
the transaction. The commit time is capped by This parameter sets the commit time (as described above) to be at least
the max_batch_time, which defaults to 15000us min_batch_time. It defaults to zero microseconds. Increasing this
(15ms). This optimization can be turned off parameter may improve the throughput of multi-threaded, synchronous
entirely by setting max_batch_time to 0. workloads on very fast disks, at the cost of increasing latency.
min_batch_time=usec This parameter sets the commit time (as journal_ioprio=prio
described above) to be at least min_batch_time. The I/O priority (from 0 to 7, where 0 is the highest priority) which
It defaults to zero microseconds. Increasing should be used for I/O operations submitted by kjournald2 during a
this parameter may improve the throughput of commit operation. This defaults to 3, which is a slightly higher
multi-threaded, synchronous workloads on very priority than the default I/O priority.
fast disks, at the cost of increasing latency.
auto_da_alloc(*), noauto_da_alloc
journal_ioprio=prio The I/O priority (from 0 to 7, where 0 is the Many broken applications don't use fsync() when replacing existing
highest priority) which should be used for I/O files via patterns such as fd = open("foo.new")/write(fd,..)/close(fd)/
operations submitted by kjournald2 during a rename("foo.new", "foo"), or worse yet, fd = open("foo",
commit operation. This defaults to 3, which is O_TRUNC)/write(fd,..)/close(fd). If auto_da_alloc is enabled, ext4
a slightly higher priority than the default I/O will detect the replace-via-rename and replace-via-truncate patterns
priority. and force that any delayed allocation blocks are allocated such that at
the next journal commit, in the default data=ordered mode, the data
auto_da_alloc(*) Many broken applications don't use fsync() when blocks of the new file are forced to disk before the rename() operation
noauto_da_alloc replacing existing files via patterns such as is committed. This provides roughly the same level of guarantees as
fd = open("foo.new")/write(fd,..)/close(fd)/ ext3, and avoids the "zero-length" problem that can happen when a
rename("foo.new", "foo"), or worse yet, system crashes before the delayed allocation blocks are forced to disk.
fd = open("foo", O_TRUNC)/write(fd,..)/close(fd).
If auto_da_alloc is enabled, ext4 will detect noinit_itable
the replace-via-rename and replace-via-truncate Do not initialize any uninitialized inode table blocks in the
patterns and force that any delayed allocation background. This feature may be used by installation CD's so that the
blocks are allocated such that at the next install process can complete as quickly as possible; the inode table
journal commit, in the default data=ordered initialization process would then be deferred until the next time the
mode, the data blocks of the new file are forced file system is unmounted.
to disk before the rename() operation is
committed. This provides roughly the same level init_itable=n
of guarantees as ext3, and avoids the The lazy itable init code will wait n times the number of milliseconds
"zero-length" problem that can happen when a it took to zero out the previous block group's inode table. This
system crashes before the delayed allocation minimizes the impact on the system performance while file system's
blocks are forced to disk. inode table is being initialized.
noinit_itable Do not initialize any uninitialized inode table discard, nodiscard(*)
blocks in the background. This feature may be Controls whether ext4 should issue discard/TRIM commands to the
used by installation CD's so that the install underlying block device when blocks are freed. This is useful for SSD
process can complete as quickly as possible; the devices and sparse/thinly-provisioned LUNs, but it is off by default
inode table initialization process would then be until sufficient testing has been done.
deferred until the next time the file system
is unmounted. nouid32
Disables 32-bit UIDs and GIDs. This is for interoperability with
init_itable=n The lazy itable init code will wait n times the older kernels which only store and expect 16-bit values.
number of milliseconds it took to zero out the
previous block group's inode table. This block_validity(*), noblock_validity
minimizes the impact on the system performance These options enable or disable the in-kernel facility for tracking
while file system's inode table is being initialized. filesystem metadata blocks within internal data structures. This
allows multi- block allocator and other routines to notice bugs or
discard Controls whether ext4 should issue discard/TRIM corrupted allocation bitmaps which cause blocks to be allocated which
nodiscard(*) commands to the underlying block device when overlap with filesystem metadata blocks.
blocks are freed. This is useful for SSD devices
and sparse/thinly-provisioned LUNs, but it is off dioread_lock, dioread_nolock
by default until sufficient testing has been done. Controls whether or not ext4 should use the DIO read locking. If the
dioread_nolock option is specified ext4 will allocate uninitialized
nouid32 Disables 32-bit UIDs and GIDs. This is for extent before buffer write and convert the extent to initialized after
interoperability with older kernels which only IO completes. This approach allows ext4 code to avoid using inode
store and expect 16-bit values. mutex, which improves scalability on high speed storages. However this
does not work with data journaling and dioread_nolock option will be
block_validity(*) These options enable or disable the in-kernel ignored with kernel warning. Note that dioread_nolock code path is only
noblock_validity facility for tracking filesystem metadata blocks used for extent-based files. Because of the restrictions this options
within internal data structures. This allows multi- comprises it is off by default (e.g. dioread_lock).
block allocator and other routines to notice
bugs or corrupted allocation bitmaps which cause max_dir_size_kb=n
blocks to be allocated which overlap with This limits the size of directories so that any attempt to expand them
filesystem metadata blocks. beyond the specified limit in kilobytes will cause an ENOSPC error.
This is useful in memory constrained environments, where a very large
dioread_lock Controls whether or not ext4 should use the DIO read directory can cause severe performance problems or even provoke the Out
dioread_nolock locking. If the dioread_nolock option is specified Of Memory killer. (For example, if there is only 512mb memory
ext4 will allocate uninitialized extent before buffer available, a 176mb directory may seriously cramp the system's style.)
write and convert the extent to initialized after IO
completes. This approach allows ext4 code to avoid i_version
using inode mutex, which improves scalability on high Enable 64-bit inode version support. This option is off by default.
speed storages. However this does not work with
data journaling and dioread_nolock option will be dax
ignored with kernel warning. Note that dioread_nolock Use direct access (no page cache). See
code path is only used for extent-based files. Documentation/filesystems/dax.txt. Note that this option is
Because of the restrictions this options comprises incompatible with data=journal.
it is off by default (e.g. dioread_lock).
max_dir_size_kb=n This limits the size of directories so that any
attempt to expand them beyond the specified
limit in kilobytes will cause an ENOSPC error.
This is useful in memory constrained
environments, where a very large directory can
cause severe performance problems or even
provoke the Out Of Memory killer. (For example,
if there is only 512mb memory available, a 176mb
directory may seriously cramp the system's style.)
i_version Enable 64-bit inode version support. This option is
off by default.
dax Use direct access (no page cache). See
Documentation/filesystems/dax.txt. Note that
this option is incompatible with data=journal.
======================= =======================================================
Data Mode Data Mode
========= =========
...@@ -407,11 +394,8 @@ in table below. ...@@ -407,11 +394,8 @@ in table below.
Files in /proc/fs/ext4/<devname> Files in /proc/fs/ext4/<devname>
================ ======= mb_groups
File Content details of multiblock allocator buddy cache of free blocks
================ =======
mb_groups details of multiblock allocator buddy cache of free blocks
================ =======
/sys entries /sys entries
============ ============
...@@ -426,74 +410,71 @@ Files in /sys/fs/ext4/<devname>: ...@@ -426,74 +410,71 @@ Files in /sys/fs/ext4/<devname>:
(see also Documentation/ABI/testing/sysfs-fs-ext4) (see also Documentation/ABI/testing/sysfs-fs-ext4)
============================= ================================================= delayed_allocation_blocks
File Content This file is read-only and shows the number of blocks that are dirty in
============================= ================================================= the page cache, but which do not have their location in the filesystem
delayed_allocation_blocks This file is read-only and shows the number of allocated yet.
blocks that are dirty in the page cache, but
which do not have their location in the inode_goal
filesystem allocated yet. Tuning parameter which (if non-zero) controls the goal inode used by
the inode allocator in preference to all other allocation heuristics.
inode_goal Tuning parameter which (if non-zero) controls This is intended for debugging use only, and should be 0 on production
the goal inode used by the inode allocator in systems.
preference to all other allocation heuristics.
This is intended for debugging use only, and inode_readahead_blks
should be 0 on production systems. Tuning parameter which controls the maximum number of inode table
blocks that ext4's inode table readahead algorithm will pre-read into
inode_readahead_blks Tuning parameter which controls the maximum the buffer cache.
number of inode table blocks that ext4's inode
table readahead algorithm will pre-read into lifetime_write_kbytes
the buffer cache This file is read-only and shows the number of kilobytes of data that
have been written to this filesystem since it was created.
lifetime_write_kbytes This file is read-only and shows the number of
kilobytes of data that have been written to this max_writeback_mb_bump
filesystem since it was created. The maximum number of megabytes the writeback code will try to write
out before move on to another inode.
max_writeback_mb_bump The maximum number of megabytes the writeback
code will try to write out before move on to mb_group_prealloc
another inode. The multiblock allocator will round up allocation requests to a
multiple of this tuning parameter if the stripe size is not set in the
mb_group_prealloc The multiblock allocator will round up allocation ext4 superblock
requests to a multiple of this tuning parameter if
the stripe size is not set in the ext4 superblock mb_max_to_scan
The maximum number of extents the multiblock allocator will search to
mb_max_to_scan The maximum number of extents the multiblock find the best extent.
allocator will search to find the best extent
mb_min_to_scan
mb_min_to_scan The minimum number of extents the multiblock The minimum number of extents the multiblock allocator will search to
allocator will search to find the best extent find the best extent.
mb_order2_req Tuning parameter which controls the minimum size mb_order2_req
for requests (as a power of 2) where the buddy Tuning parameter which controls the minimum size for requests (as a
cache is used power of 2) where the buddy cache is used.
mb_stats Controls whether the multiblock allocator should mb_stats
collect statistics, which are shown during the Controls whether the multiblock allocator should collect statistics,
unmount. 1 means to collect statistics, 0 means which are shown during the unmount. 1 means to collect statistics, 0
not to collect statistics means not to collect statistics.
mb_stream_req Files which have fewer blocks than this tunable mb_stream_req
parameter will have their blocks allocated out Files which have fewer blocks than this tunable parameter will have
of a block group specific preallocation pool, so their blocks allocated out of a block group specific preallocation
that small files are packed closely together. pool, so that small files are packed closely together. Each large file
Each large file will have its blocks allocated will have its blocks allocated out of its own unique preallocation
out of its own unique preallocation pool. pool.
session_write_kbytes This file is read-only and shows the number of session_write_kbytes
kilobytes of data that have been written to this This file is read-only and shows the number of kilobytes of data that
filesystem since it was mounted. have been written to this filesystem since it was mounted.
reserved_clusters This is RW file and contains number of reserved reserved_clusters
clusters in the file system which will be used This is RW file and contains number of reserved clusters in the file
in the specific situations to avoid costly system which will be used in the specific situations to avoid costly
zeroout, unexpected ENOSPC, or possible data zeroout, unexpected ENOSPC, or possible data loss. The default is 2% or
loss. The default is 2% or 4096 clusters, 4096 clusters, whichever is smaller and this can be changed however it
whichever is smaller and this can be changed can never exceed number of clusters in the file system. If there is not
however it can never exceed number of clusters enough space for the reserved space when mounting the file mount will
in the file system. If there is not enough space _not_ fail.
for the reserved space when mounting the file
mount will _not_ fail.
============================= =================================================
Ioctls Ioctls
====== ======
...@@ -504,100 +485,80 @@ shown in the table below. ...@@ -504,100 +485,80 @@ shown in the table below.
Table of Ext4 specific ioctls Table of Ext4 specific ioctls
============================= ================================================= EXT4_IOC_GETFLAGS
Ioctl Description Get additional attributes associated with inode. The ioctl argument is
============================= ================================================= an integer bitfield, with bit values described in ext4.h. This ioctl is
EXT4_IOC_GETFLAGS Get additional attributes associated with inode. an alias for FS_IOC_GETFLAGS.
The ioctl argument is an integer bitfield, with
bit values described in ext4.h. This ioctl is an EXT4_IOC_SETFLAGS
alias for FS_IOC_GETFLAGS. Set additional attributes associated with inode. The ioctl argument is
an integer bitfield, with bit values described in ext4.h. This ioctl is
EXT4_IOC_SETFLAGS Set additional attributes associated with inode. an alias for FS_IOC_SETFLAGS.
The ioctl argument is an integer bitfield, with
bit values described in ext4.h. This ioctl is an EXT4_IOC_GETVERSION, EXT4_IOC_GETVERSION_OLD
alias for FS_IOC_SETFLAGS. Get the inode i_generation number stored for each inode. The
i_generation number is normally changed only when new inode is created
EXT4_IOC_GETVERSION and it is particularly useful for network filesystems. The '_OLD'
EXT4_IOC_GETVERSION_OLD version of this ioctl is an alias for FS_IOC_GETVERSION.
Get the inode i_generation number stored for
each inode. The i_generation number is normally EXT4_IOC_SETVERSION, EXT4_IOC_SETVERSION_OLD
changed only when new inode is created and it is Set the inode i_generation number stored for each inode. The '_OLD'
particularly useful for network filesystems. The version of this ioctl is an alias for FS_IOC_SETVERSION.
'_OLD' version of this ioctl is an alias for
FS_IOC_GETVERSION. EXT4_IOC_GROUP_EXTEND
This ioctl has the same purpose as the resize mount option. It allows
EXT4_IOC_SETVERSION to resize filesystem to the end of the last existing block group,
EXT4_IOC_SETVERSION_OLD further resize has to be done with resize2fs, either online, or
Set the inode i_generation number stored for offline. The argument points to the unsigned logn number representing
each inode. The '_OLD' version of this ioctl the filesystem new block count.
is an alias for FS_IOC_SETVERSION.
EXT4_IOC_MOVE_EXT
EXT4_IOC_GROUP_EXTEND This ioctl has the same purpose as the resize Move the block extents from orig_fd (the one this ioctl is pointing to)
mount option. It allows to resize filesystem to the donor_fd (the one specified in move_extent structure passed as
to the end of the last existing block group, an argument to this ioctl). Then, exchange inode metadata between
further resize has to be done with resize2fs, orig_fd and donor_fd. This is especially useful for online
either online, or offline. The argument points defragmentation, because the allocator has the opportunity to allocate
to the unsigned logn number representing the moved blocks better, ideally into one contiguous extent.
filesystem new block count.
EXT4_IOC_GROUP_ADD
EXT4_IOC_MOVE_EXT Move the block extents from orig_fd (the one Add a new group descriptor to an existing or new group descriptor
this ioctl is pointing to) to the donor_fd (the block. The new group descriptor is described by ext4_new_group_input
one specified in move_extent structure passed structure, which is passed as an argument to this ioctl. This is
as an argument to this ioctl). Then, exchange especially useful in conjunction with EXT4_IOC_GROUP_EXTEND, which
inode metadata between orig_fd and donor_fd. allows online resize of the filesystem to the end of the last existing
This is especially useful for online block group. Those two ioctls combined is used in userspace online
defragmentation, because the allocator has the resize tool (e.g. resize2fs).
opportunity to allocate moved blocks better,
ideally into one contiguous extent. EXT4_IOC_MIGRATE
This ioctl operates on the filesystem itself. It converts (migrates)
EXT4_IOC_GROUP_ADD Add a new group descriptor to an existing or ext3 indirect block mapped inode to ext4 extent mapped inode by walking
new group descriptor block. The new group through indirect block mapping of the original inode and converting
descriptor is described by ext4_new_group_input contiguous block ranges into ext4 extents of the temporary inode. Then,
structure, which is passed as an argument to inodes are swapped. This ioctl might help, when migrating from ext3 to
this ioctl. This is especially useful in ext4 filesystem, however suggestion is to create fresh ext4 filesystem
conjunction with EXT4_IOC_GROUP_EXTEND, and copy data from the backup. Note, that filesystem has to support
which allows online resize of the filesystem extents for this ioctl to work.
to the end of the last existing block group.
Those two ioctls combined is used in userspace EXT4_IOC_ALLOC_DA_BLKS
online resize tool (e.g. resize2fs). Force all of the delay allocated blocks to be allocated to preserve
application-expected ext3 behaviour. Note that this will also start
EXT4_IOC_MIGRATE This ioctl operates on the filesystem itself. triggering a write of the data blocks, but this behaviour may change in
It converts (migrates) ext3 indirect block mapped the future as it is not necessary and has been done this way only for
inode to ext4 extent mapped inode by walking sake of simplicity.
through indirect block mapping of the original
inode and converting contiguous block ranges EXT4_IOC_RESIZE_FS
into ext4 extents of the temporary inode. Then, Resize the filesystem to a new size. The number of blocks of resized
inodes are swapped. This ioctl might help, when filesystem is passed in via 64 bit integer argument. The kernel
migrating from ext3 to ext4 filesystem, however allocates bitmaps and inode table, the userspace tool thus just passes
suggestion is to create fresh ext4 filesystem the new number of blocks.
and copy data from the backup. Note, that
filesystem has to support extents for this ioctl EXT4_IOC_SWAP_BOOT
to work. Swap i_blocks and associated attributes (like i_blocks, i_size,
i_flags, ...) from the specified inode with inode EXT4_BOOT_LOADER_INO
EXT4_IOC_ALLOC_DA_BLKS Force all of the delay allocated blocks to be (#5). This is typically used to store a boot loader in a secure part of
allocated to preserve application-expected ext3 the filesystem, where it can't be changed by a normal user by accident.
behaviour. Note that this will also start The data blocks of the previous boot loader will be associated with the
triggering a write of the data blocks, but this given inode.
behaviour may change in the future as it is
not necessary and has been done this way only
for sake of simplicity.
EXT4_IOC_RESIZE_FS Resize the filesystem to a new size. The number
of blocks of resized filesystem is passed in via
64 bit integer argument. The kernel allocates
bitmaps and inode table, the userspace tool thus
just passes the new number of blocks.
EXT4_IOC_SWAP_BOOT Swap i_blocks and associated attributes
(like i_blocks, i_size, i_flags, ...) from
the specified inode with inode
EXT4_BOOT_LOADER_INO (#5). This is typically
used to store a boot loader in a secure part of
the filesystem, where it can't be changed by a
normal user by accident.
The data blocks of the previous boot loader
will be associated with the given inode.
============================= =================================================
References References
========== ==========
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7