Lines Matching +full:ext2 +full:- +full:buffer +full:- +full:low +full:- +full:power
1 .. SPDX-License-Identifier: GPL-2.0
9 (64 bit) in keeping with increasing disk capacities and state-of-the-art
12 Mailing list: linux-ext4@vger.kernel.org
23 - The latest version of e2fsprogs can be found at:
33 https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
35 - Create a new filesystem using the ext4 filesystem type:
37 # mke2fs -t ext4 /dev/hda1
41 # tune2fs -O extents /dev/hda1
46 # tune2fs -I 256 /dev/hda1
48 - Mounting:
50 # mount -t ext4 /dev/hda1 /wherever
52 - When comparing performance with other filesystems, it's always
59 '-o barriers=[0|1]' mount option for both ext3 and ext4 filesystems
61 it is often worthwhile to try changing the data journaling mode; '-o
67 metadata-intensive workloads.
73 -------------------
77 * extent format more robust in face of on-disk corruption due to magics,
79 * improved file allocation (multi-block alloc)
92 * efficient new ordered mode in JBD2 and ext4 (avoid using buffer head to force
94 * Case-insensitive file name lookups
95 * file-based encryption support (fscrypt)
96 * file-based verity support (fsverity)
101 case-insensitive file name lookups
104 The case-insensitive file name lookup feature is supported on a
105 per-directory basis, allowing the user to mix case-insensitive and
106 case-sensitive directories in the same filesystem. It is enabled by
108 case-insensitive string match operation is only defined when we know how
110 case-insensitive directories, the filesystem must have the
111 casefold feature, which stores the filesystem-wide encoding
113 Unicode (12.1.0, by the time of this writing), encoded in the UTF-8
118 The case-awareness is name-preserving on the disk, meaning that the file
119 name provided by userspace is a byte-per-byte match to what is actually
123 used on large case-insensitive directories with DX feature. On DX
136 operate on that file, but the case-insensitive lookups won't work.
188 you lose your power, you will lose as much as the latest 5 seconds of
190 to the journaling). This default value (or any low value) will hurt
191 performance, but it's good for data-safety. Setting it to 0 will have
194 delayed allocation even older data can be lost on power failure since
203 proper on-disk ordering of journal commits, making volatile disk write
205 battery-backed in one way or another, disabling barriers may safely
212 that ext4's inode table readahead algorithm will pre-read into the
213 buffer cache. The default value is 32 blocks.
229 errors=remount-ro
230 Remount the filesystem read-only on an error.
241 Just print an error message if an error occurs in a file data buffer.
244 Abort the journal if an error occurs in a file data buffer.
264 documentation in the quota-tools package for more details
270 the above quota options. See documentation in the quota-tools package
308 parameter may improve the throughput of multi-threaded, synchronous
322 will detect the replace-via-rename and replace-via-truncate patterns
327 ext3, and avoids the "zero-length" problem that can happen when a
346 devices and sparse/thinly-provisioned LUNs, but it is off by default
350 Disables 32-bit UIDs and GIDs. This is for interoperability with
351 older kernels which only store and expect 16-bit values.
354 These options enable or disable the in-kernel facility for tracking
356 allows multi- block allocator and other routines to notice bugs or
363 extent before buffer write and convert the extent to initialized after
368 used for extent-based files. Because of the restrictions this options
380 Enable 64-bit inode version support. This option is off by default.
389 blk-crypto framework rather than filesystem-layer encryption. This
390 allows the use of inline encryption hardware. The on-disk format is
392 Documentation/block/inline-encryption.rst.
402 mode - metadata journaling. A crash+recovery can cause incorrect data to
431 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
445 /sys/fs/ext4/dm-0). The files in each per-device directory are shown
450 (see also Documentation/ABI/testing/sysfs-fs-ext4)
453 This file is read-only and shows the number of blocks that are dirty in
458 Tuning parameter which (if non-zero) controls the goal inode used by
465 blocks that ext4's inode table readahead algorithm will pre-read into
466 the buffer cache.
469 This file is read-only and shows the number of kilobytes of data that
491 power of 2) where the buddy cache is used.
506 This file is read-only and shows the number of kilobytes of data that
522 ext4-specific functionality. An incomplete list of these ioctls is shown in the
523 table below. This list includes truly ext4-specific ioctls (``EXT4_IOC_*``) as
524 well as ioctls that may have been ext4-specific originally but are now supported
583 application-expected ext3 behaviour. Note that this will also start
610 useful links: https://fedoraproject.org/wiki/ext3-devel