Debian Codegraph @

upstream/debian-unstable/man8/tune2fs.8

raw
1 .\" Revision 1.0 93/06/3 23:00 chk
2 .\" Initial revision
3 .\"
4 .\"
5 .TH TUNE2FS 8 "March 2025" "E2fsprogs version 1.47.4"
6 .SH NAME
7 tune2fs \- adjust tunable file system parameters on ext2/ext3/ext4 file systems
8 .SH SYNOPSIS
9 .B tune2fs
10 [
11 .B \-l
12 ]
13 [
14 .BI \-c " max-mount-counts"
15 ]
16 [
17 .BI \-e " errors-behavior"
18 ]
19 [
20 .B \-f
21 ]
22 [
23 .BI \-i " interval-between-checks"
24 ]
25 [
26 .BI \-I " new_inode_size"
27 ]
28 [
29 .B \-j
30 ]
31 [
32 .BI \-J " journal-options"
33 ]
34 [
35 .BI \-m " reserved-blocks-percentage"
36 ]
37 [
38 .B \-o\fR [\fB^\fR]\fImount-options\fR[,...]
39 ]
40 [
41 .BI \-r " reserved-blocks-count"
42 ]
43 [
44 .BI \-u " user"
45 ]
46 [
47 .BI \-g " group"
48 ]
49 [
50 .BI \-C " mount-count"
51 ]
52 [
53 .BI \-E " extended-options"
54 ]
55 [
56 .BI \-L " volume-label"
57 ]
58 [
59 .BI \-M " last-mounted-directory"
60 ]
61 [
62 .B \-O\fR [\fB^\fR]\fIfeature\fR[,...]
63 ]
64 [
65 .BI \-Q " quota-options"
66 ]
67 [
68 .BI \-T " time-last-checked"
69 ]
70 [
71 .BI \-U " UUID"
72 ]
73 [
74 .BI \-z " undo_file"
75 ]
76 device
77 .SH DESCRIPTION
78 .B tune2fs
79 allows the system administrator to adjust various tunable file system
80 parameters on Linux ext2, ext3, or ext4 file systems. The current values
81 of these options can be displayed by using the \fB\-l\fR option to
82 \fBtune2fs\fR(8) program, or by using the \fBdumpe2fs\fR(8) program.
83 .PP
84 The \fIdevice\fR
85 specifier can either be a filename (i.e., /dev/sda1), or a LABEL or UUID
86 specifier: "\fBLABEL=\fIvolume-label\fR" or "\fBUUID=\fIuuid\fR". (i.e.,
87 LABEL=home or UUID=e40486c6-84d5-4f2f-b99c-032281799c9d).
88 .SH OPTIONS
89 .TP
90 .BI \-c " max-mount-counts"
91 Adjust the number of mounts after which the file system will be checked by
92 \fBe2fsck\fR(8). If \fImax-mount-counts\fR
93 is the string "random", tune2fs will use a random value between 20 and 40.
94 If \fImax-mount-counts\fR
95 is 0 or \-1, the number of times the file system is mounted will be disregarded
96 by \fBe2fsck\fR(8) and the kernel.
97 .sp
98 Staggering the mount-counts at which file systems are forcibly
99 checked will avoid all file systems being checked at one time
100 when using journaled file systems.
101 .sp
102 Mount-count-dependent checking is disabled by default to avoid
103 unanticipated long reboots while \fBe2fsck\fR(8) does its work. If you
104 are concerned about file system corruptions caused by potential hardware
105 problems of kernel bugs, a better solution than mount-count-dependent
106 checking is to use the \fBe2scrub\fR(8)
107 program. This does require placing the file system on an LVM volume,
108 however.
109 .TP
110 .BI \-C " mount-count"
111 Set the number of times the file system has been mounted.
112 If set to a greater value than the max-mount-counts parameter
113 set by the \fB\-c\fR option, \fBe2fsck\fR(8)
114 will check the file system at the next reboot.
115 .TP
116 .BI \-e " error-behavior"
117 Change the behavior of the kernel code when errors are detected.
118 In all cases, a file system error will cause \fBe2fsck\fR(8)
119 to check the file system on the next boot. \fIerror-behavior\fR
120 can be one of the following:
121 .RS 1.2i
122 .TP 1.2i
123 .B continue
124 Continue normal execution.
125 .TP
126 .B remount-ro
127 Remount file system read-only.
128 .TP
129 .B panic
130 Cause a kernel panic.
131 .RE
132 .TP
133 .BI \-E " extended-options"
134 Set extended options for the file system. Extended options are comma
135 separated, and may take an argument using the equals ('=') sign.
136 The following extended options are supported:
137 .RS 1.2i
138 .TP
139 .B clear_mmp
140 Reset the MMP block (if any) back to the clean state. Use only if
141 absolutely certain the device is not currently mounted or being
142 fscked, or major file system corruption can result. Needs \fB\-f\fR.
143 .TP
144 .BI encoding= encoding-name
145 Enable the \fBcasefold\fR feature in the super block and set
146 \fIencoding-name\fR as the encoding to be used. If \fIencoding-name\fR
147 is not specified, "utf8" is used. The encoding cannot be altered if
148 \fBcasefold\fR was previously enabled.
149 .TP
150 .BI encoding_flags= encoding-flags
151 Define parameters for file name character encoding operations. If a
152 flag is not changed using this parameter, its default value is used.
153 \fIencoding-flags\fR
154 should be a comma-separated lists of flags to be enabled. The flags cannot be
155 altered if \fBcasefold\fR was previously enabled.
156
157 The only flag that can be set right now is \fIstrict\fR
158 which means that invalid strings should be rejected by the file system.
159 In the default configuration, the \fIstrict\fR flag is disabled.
160 .TP
161 .B force_fsck
162 Set a flag in the file system superblock indicating that errors have been found.
163 This will force fsck to run at the next mount.
164 .TP
165 .BI hash_alg= hash-alg
166 Set the default hash algorithm used for file systems with hashed b-tree
167 directories. Valid algorithms accepted are:
168 .BR legacy ,
169 .BR half_md4 ,
170 and
171 .BR tea .
172 .TP
173 .BI mmp_update_interval= interval
174 Adjust the initial MMP update interval to \fIinterval\fR
175 seconds. Specifying an \fIinterval\fR
176 of 0 means to use the default interval. The specified interval must
177 be less than 300 seconds. Requires that the \fBmmp\fR feature be enabled.
178 .TP
179 .BI mount_opts= mount_option_string
180 Set a set of default mount options which will be used when the file
181 system is mounted. Unlike the bitmask-based default mount options which
182 can be specified with the \fB\-o\fR option, \fImount_option_string\fR
183 is an arbitrary string with a maximum length of 63 bytes, which is
184 stored in the superblock.
185 .IP
186 The ext4 file system driver will first apply
187 the bitmask-based default options, and then parse the \fImount_option_string\fR,
188 before parsing the mount options passed from the \fBmount\fR(8) program.
189 .IP
190 This superblock setting is only honored in 2.6.35+ kernels;
191 and not at all by the ext2 and ext3 file system drivers.
192 .TP
193 .BI orphan_file_size= size
194 Set size of the file for tracking unlinked but still open inodes and inodes
195 with truncate in progress. Larger file allows for better scalability,
196 reserving a few blocks per CPU is ideal.
197 .TP
198 .BI stride= stride-size
199 Configure the file system for a RAID array with \fIstride-size\fR
200 file system blocks. This is the number of blocks read or written to disk
201 before moving to next disk. This mostly affects placement of file system
202 metadata like bitmaps at \fBmke2fs\fR(8)
203 time to avoid placing them on a single disk, which can hurt the performance.
204 It may also be used by block allocator.
205 .TP
206 .BI stripe_width= stripe-width
207 Configure the file system for a RAID array with \fIstripe-width\fR
208 file system blocks per stripe. This is typically be stride-size * N, where
209 N is the number of data disks in the RAID (e.g. RAID 5 N+1, RAID 6 N+2).
210 This allows the block allocator to prevent read-modify-write of the
211 parity in a RAID stripe if possible when the data is written.
212 .TP
213 .B test_fs
214 Set a flag in the file system superblock indicating that it may be
215 mounted using experimental kernel code, such as the ext4dev file system.
216 .TP
217 .B ^test_fs
218 Clear the test_fs flag, indicating the file system should only be mounted
219 using production-level file system code.
220 .RE
221 .TP
222 .B \-f
223 Force the \fBtune2fs\fR operation to complete even in the face of errors. This
224 option is useful when removing the \fBhas_journal\fR
225 file system feature from a file system which has
226 an external journal (or is corrupted
227 such that it appears to have an external journal), but that
228 external journal is not available. If the file system appears to require
229 journal replay, the \fB\-f\fR flag must be specified twice to proceed.
230 .sp
231 .B Warning:
232 Removing an external journal from a file system which was not cleanly unmounted
233 without first replaying the external journal can result in
234 severe data loss and file system corruption.
235 .TP
236 .BI \-g " group"
237 Set the group which can use the reserved file system blocks. The \fIgroup\fR
238 parameter can be a numerical gid or a group name. If a group name is given,
239 it is converted to a numerical gid before it is stored in the superblock.
240 .TP
241 .B \-i " \fIinterval-between-checks\fR[\fBd\fR|\fBm\fR|\fBw\fR]"
242 Adjust the maximal time between two file system checks.
243 No suffix or \fBd\fR will interpret the number \fIinterval-between-checks\fR
244 as days, \fBm\fR as months, and \fBw\fR
245 as weeks. A value of zero will disable the time-dependent checking.
246 .sp
247 There are pros and cons to disabling these periodic checks; see the
248 discussion under the \fB\-c\fR (mount-count-dependent check) option for details.
249 .TP
250 .B \-I
251 Change the inode size used by the file system. This requires rewriting
252 the inode table, so it requires that the file system is checked for
253 consistency first using \fBe2fsck\fR(8).
254 This operation can also take a while and the file system can be
255 corrupted and data lost if it is interrupted while in the middle of
256 converting the file system. Backing up the file system before changing
257 inode size is recommended.
258 .IP
259 File systems with an inode size of 128 bytes do not support timestamps
260 beyond January 19, 2038. Inodes which are 256 bytes or larger will
261 support extended timestamps, project id's, and the ability to store some
262 extended attributes in the inode table for improved performance.
263 .TP
264 .B \-j
265 Add an ext3 journal to the file system. If the \fB\-J\fR
266 option is not specified, the default journal parameters will be used to create
267 an appropriately sized journal (given the size of the file system)
268 stored within the file system. Note that you must be using a kernel
269 which has ext3 support in order to actually make use of the journal.
270 .IP
271 If this option is used to create a journal on a mounted file system, an
272 immutable file, \fB.journal\fR,
273 will be created in the top-level directory of the file system, as it is
274 the only safe way to create the journal inode while the file system is
275 mounted. While the ext3 journal is visible, it is not safe to
276 delete it, or modify it while the file system is mounted; for this
277 reason the file is marked immutable. While checking unmounted file systems,
278 \fBe2fsck\fR(8) will automatically move \fB.journal\fR
279 files to the invisible, reserved journal inode. For all file systems
280 except for the root file system, this should happen automatically and
281 naturally during the next reboot cycle. Since the root file system is
282 mounted read-only, \fBe2fsck\fR(8)
283 must be run from a rescue floppy in order to effect this transition.
284 .IP
285 On some distributions, such as Debian, if an initial ramdisk is used,
286 the initrd scripts will automatically convert an ext2 root file system
287 to ext3 if the \fB/etc/fstab\fR(5)
288 file specifies the ext3 file system for the root file system in order to
289 avoid requiring the use of a rescue floppy to add an ext3 journal to
290 the root file system.
291 .TP
292 .BR \-J " journal-options"
293 Override the default ext3 journal parameters. Journal options are comma
294 separated, and may take an argument using the equals ('=') sign.
295 The following journal options are supported:
296 .RS 1.2i
297 .TP
298 .BI device= external-journal
299 Attach the file system to the journal block device located on
300 \fIexternal-journal\fR. The external
301 journal must have been already created using the command
302 .IP
303 .B mke2fs \-O journal_dev
304 .I external-journal
305 .IP
306 Note that \fIexternal-journal\fR must be formatted with the same block
307 size as file systems which will be using it.
308 In addition, while there is support for attaching
309 multiple file systems to a single external journal,
310 the Linux kernel and \fBe2fsck\fR(8)
311 do not currently support shared external journals yet.
312 .IP
313 Instead of specifying a device name directly, \fIexternal-journal\fR
314 can also be specified by either \fBLABEL=\fIlabel\fR or \fBUUID=\fIUUID\fR
315 to locate the external journal by either the volume label or UUID
316 stored in the ext2 superblock at the start of the journal. Use
317 \fBdumpe2fs\fR(8)
318 to display a journal device's volume label and UUID. See also the
319 \fB\-L\fR option of \fBtune2fs\fR(8).
320 .TP
321 .BI fast_commit_size= fast-commit-size
322 Create an additional fast commit journal area of size \fIfast-commit-size\fR
323 kilobytes. This option is only valid if \fBfast_commit\fR feature is enabled
324 on the file system. If this option is not specified and if \fBfast_commit\fR
325 feature is turned on, fast commit area size defaults to \fIjournal-size\fR
326 / 64 megabytes. The total size of the journal with \fBfast_commit\fR
327 feature set is \fIjournal-size\fR + ( \fIfast-commit-size\fR * 1024 )
328 megabytes. The total journal size may be no more than
329 10,240,000 file system blocks or half the total file system size
330 (whichever is smaller).
331 .TP
332 .BI location =journal-location
333 Specify the location of the journal. The argument \fIjournal-location\fR
334 can either be specified as a block number, or if the number has a units
335 suffix (e.g., 'M', 'G', etc.) interpret it as the offset from the
336 beginning of the file system.
337 .TP
338 .BI size= journal-size
339 Create a journal stored in the file system of size \fIjournal-size\fR
340 megabytes. The size of the journal must be at least 1024 file system blocks
341 (i.e., 1\~MiB if using 1k blocks, 4\~MiB if using 4k blocks, etc.)
342 and may be no more than 10,240,000 file system blocks.
343 There must be enough free space in the file system to create a journal of
344 that size.
345 .RE
346 .IP
347 Only one of the \fBsize\fR or \fBdevice\fR
348 options can be given for a file system.
349 .TP
350 .B \-l
351 List the contents of the file system superblock, including the current
352 values of the parameters that can be set via this program.
353 .TP
354 .BI \-L " volume-label"
355 Set the volume label of the file system.
356 Ext2 file system labels can be at most 16 characters long; if \fIvolume-label\fR
357 is longer than 16 characters, \fBtune2fs\fR
358 will truncate it and print a warning. For other file systems that
359 support online label manipulation and are mounted \fBtune2fs\fR
360 will work as well, but it will not attempt to truncate the \fIvolume-label\fR
361 at all. The volume label can be used by \fBmount\fR(8), \fBfsck\fR(8),
362 and \fB/etc/fstab\fR(5) (and possibly others) by specifying
363 \fBLABEL=\fIvolume-label\fR instead of a block special device name like
364 \fI/dev/hda5\fR.
365 .TP
366 .BI \-m " reserved-blocks-percentage"
367 Set the percentage of the file system which may only be allocated
368 by privileged processes. Reserving some number of file system blocks
369 for use by privileged processes is done
370 to avoid file system fragmentation, and to allow system
371 daemons, such as \fBsyslogd\fR(8),
372 to continue to function correctly after non-privileged processes are
373 prevented from writing to the file system. Normally, the default percentage
374 of reserved blocks is 5%.
375 .TP
376 .BI \-M " last-mounted-directory"
377 Set the last-mounted directory for the file system.
378 .TP
379 .B \-o "\fR[\fB^\fR]\fImount-option\fR[,...]"
380 Set or clear the indicated default mount options in the file system.
381 Default mount options can be overridden by mount options specified
382 either in \fB/etc/fstab\fR(5) or on the command line arguments to \fBmount\fR(8).
383 Older kernels may not support this feature; in particular,
384 kernels which predate 2.4.20 will almost certainly ignore the
385 default mount options field in the superblock.
386 .IP
387 More than one mount option can be cleared or set by separating
388 features with commas. Mount options prefixed with a
389 caret character ('^') will be cleared in the file system's superblock;
390 mount options without a prefix character or prefixed with a plus
391 character ('+') will be added to the file system.
392 .IP
393 The following mount options can be set or cleared using \fBtune2fs\fR:
394 .RS 1.2i
395 .TP
396 .B debug
397 Enable debugging code for this file system.
398 .TP
399 .B bsdgroups
400 Emulate BSD behavior when creating new files: they will take the group-id
401 of the directory in which they were created. The standard System V behavior
402 is the default, where newly created files take on the fsgid of the current
403 process, unless the directory has the setgid bit set, in which case it takes
404 the gid from the parent directory, and also gets the setgid bit set if it is
405 a directory itself.
406 .TP
407 .B user_xattr
408 Enable user-specified extended attributes.
409 .TP
410 .B acl
411 Enable Posix Access Control Lists.
412 .TP
413 .B uid16
414 Disables 32-bit UIDs and GIDs. This is for interoperability with
415 older kernels which only store and expect 16-bit values.
416 .TP
417 .B journal_data
418 When the file system is mounted with journaling enabled, all data
419 (not just metadata) is committed into the journal prior to being written
420 into the main file system.
421 .TP
422 .B journal_data_ordered
423 When the file system is mounted with journaling enabled, all data is forced
424 directly out to the main file system prior to its metadata being committed
425 to the journal.
426 .TP
427 .B journal_data_writeback
428 When the file system is mounted with journaling enabled, data may be
429 written into the main file system after its metadata has been committed
430 to the journal. This may increase throughput, however, it may allow old
431 data to appear in files after a crash and journal recovery.
432 .TP
433 .B nobarrier
434 The file system will be mounted with barrier operations in the journal
435 disabled. (This option is currently only supported by the ext4 file
436 system driver in 2.6.35+ kernels.)
437 .TP
438 .B block_validity
439 The file system will be mounted with the block_validity option enabled,
440 which causes extra checks to be performed after reading or writing from
441 the file system. This prevents corrupted metadata blocks from causing
442 file system damage by overwriting parts of the inode table or block
443 group descriptors. This comes at the cost of increased memory and CPU
444 overhead, so it is enabled only for debugging purposes. (This option is
445 currently only supported by the ext4 file system driver in 2.6.35+
446 kernels.)
447 .TP
448 .B discard
449 The file system will be mounted with the \fBdiscard\fR mount option. This will
450 cause the file system driver to attempt to use the trim/discard feature
451 of some storage devices (such as SSD's and thin-provisioned drives
452 available in some enterprise storage arrays) to inform the storage
453 device that blocks belonging to deleted files can be reused for other
454 purposes. (This option is currently only supported by the ext4 file
455 system driver in 2.6.35+ kernels.)
456 .TP
457 .B nodelalloc
458 The file system will be mounted with the \fBnodelalloc\fR mount option. This
459 will disable the delayed allocation feature. (This option is currently
460 only supported by the ext4 file system driver in 2.6.35+ kernels.)
461 .RE
462 .TP
463 .B \-O "\fR[\fB^\fR]\fIfeature\fR[,...]"
464 Set or clear the indicated file system features (options) in the file system.
465 More than one file system feature can be cleared or set by separating
466 features with commas. File System features prefixed with a
467 caret character ('^') will be cleared in the file system's superblock;
468 file system features without a prefix character or prefixed with a plus
469 character ('+') will be added to the file system. For a detailed
470 description of the file system features, please see the man page \fBext4\fR(5).
471 .IP
472 The following file system features can be set or cleared using
473 .BR tune2fs :
474 .RS 1.2i
475 .TP
476 .B 64bit
477 Enable the file system to be larger than 2^32 blocks.
478 .TP
479 .B casefold
480 Enable support for file system level casefolding.
481 The option can be cleared only if filesystem has no directories with \fBF\fR
482 attribute.
483 .TP
484 .B dir_index
485 Use hashed b-trees to speed up lookups for large directories.
486 .TP
487 .B dir_nlink
488 Allow more than 65000 subdirectories per directory.
489 .TP
490 .B ea_inode
491 Allow the value of each extended attribute to be placed in the data blocks of a
492 separate inode if necessary, increasing the limit on the size and number of
493 extended attributes per file.
494 \fBtune2fs\fR currently only supports setting this file system feature.
495 .TP
496 .B encrypt
497 Enable support for file system level encryption.
498 \fBtune2fs\fR currently only supports setting this file system feature.
499 .TP
500 .B extent
501 Enable the use of extent trees to store the location of data blocks in inodes.
502 \fBtune2fs\fR currently only supports setting this file system feature.
503 .TP
504 .B extra_isize
505 Enable the extended inode fields used by ext4.
506 .TP
507 .B filetype
508 Store file type information in directory entries.
509 .TP
510 .B flex_bg
511 Allow bitmaps and inode tables for a block group to be placed
512 anywhere on the storage media. \fBtune2fs\fR will not reorganize
513 the location of the inode tables and allocation bitmaps, as \fBmke2fs\fR(8)
514 will do when it creates a freshly formatted file system with \fBflex_bg\fR
515 enabled.
516 .TP
517 .B has_journal
518 Use a journal to ensure file system consistency even across unclean shutdowns.
519 Setting the file system feature is equivalent to using the \fB\-j\fR option.
520 .TP
521 .B fast_commit
522 Enable fast commit journaling feature to improve fsync latency.
523 .TP
524 .B large_dir
525 Increase the limit on the number of files per directory.
526 \fBtune2fs\fR currently only supports setting this file system feature.
527 .TP
528 .B huge_file
529 Support files larger than 2 terabytes in size.
530 .TP
531 .B large_file
532 File System can contain files that are greater than 2\~GiB.
533 .TP
534 .B metadata_csum
535 Store a checksum to protect the contents in each metadata block.
536 .TP
537 .B metadata_csum_seed
538 Allow the file system to store the metadata checksum seed in the
539 superblock, enabling the administrator to change the UUID of a file system
540 using the \fBmetadata_csum\fR feature while it is mounted.
541 .TP
542 .B mmp
543 Enable or disable multiple mount protection (MMP) feature.
544 .TP
545 .B orphan_file
546 Store the list of orphan inodes in multiple blocks instead of a single
547 linked-list to avoid potential scalability bottlenecks for workloads
548 that perform a large number of file truncations or extensions in parallel.
549 .TP
550 .B project
551 Enable project ID tracking. This is used for project quota tracking.
552 .TP
553 .B quota
554 Enable internal file system quota inodes.
555 .TP
556 .B read-only
557 Force the kernel to mount the file system read-only.
558 .TP
559 .B resize_inode
560 Reserve space so the block group descriptor table may grow in the future.
561 \fBtune2fs\fR only supports clearing this file system feature.
562 .TP
563 .B sparse_super
564 Limit the number of backup superblocks to save space on large file systems.
565 \fBtune2fs\fR currently only supports setting this file system feature.
566 .TP
567 .B stable_inodes
568 Prevent the file system from being shrunk or having its UUID changed, in order to
569 allow the use of specialized encryption settings that make use of the inode
570 numbers and UUID.
571 \fBtune2fs\fR currently only supports setting this file system feature.
572 .TP
573 .B uninit_bg
574 Allow the kernel to initialize bitmaps and inode tables lazily, and to
575 keep a high watermark for the unused inodes in a file system, to reduce
576 \fBe2fsck\fR(8)
577 time. The first \fBe2fsck\fR(8) run after enabling this feature will take the
578 full time, but subsequent \fBe2fsck\fR(8) runs will take only a fraction of the
579 original time, depending on how full the file system is.
580 .TP
581 .B verity
582 Enable support for verity protected files.
583 \fBtune2fs\fR currently only supports setting this file system feature.
584 .RE
585 .IP
586 After setting or clearing
587 .BR sparse_super ,
588 .BR uninit_bg ,
589 .BR filetype ,
590 or
591 .B resize_inode
592 file system features, the file system may require being checked using
593 \fBe2fsck\fR(8) to return the file system to a consistent state.
594 \fBtune2fs\fR will print a message requesting that the system administrator run
595 \fBe2fsck\fR(8) if necessary. After setting the \fBdir_index\fR feature,
596 \fBe2fsck \-D\fR
597 can be run to convert existing directories to the hashed B-tree format.
598 Enabling certain file system features may prevent the file system from being
599 mounted by kernels which do not support those features. In particular, the
600 \fBuninit_bg\fR and \fBflex_bg\fR
601 features are only supported by the ext4 file system.
602 .TP
603 .BI \-r " reserved-blocks-count"
604 Set the number of reserved file system blocks.
605 .TP
606 .BI \-Q " quota-options"
607 Sets the \fBquota\fR feature on the superblock and works on the quota files for the
608 given quota type. Quota options could be one or more of the following:
609 .RS 1.2i
610 .TP
611 .RB [ ^ ] usrquota
612 Sets/clears user quota inode in the superblock.
613 .TP
614 .RB [ ^ ] grpquota
615 Sets/clears group quota inode in the superblock.
616 .TP
617 .RB [ ^ ] prjquota
618 Sets/clears project quota inode in the superblock.
619 .RE
620 .TP
621 .BI \-T " time-last-checked"
622 Set the time the file system was last checked using \fBe2fsck\fR.
623 The time is interpreted using the current (local) timezone.
624 This can be useful in scripts which use a Logical Volume Manager to make
625 a consistent snapshot of a file system, and then check the file system
626 during off hours to make sure it hasn't been corrupted due to
627 hardware problems, etc. If the file system was clean, then this option can
628 be used to set the last checked time on the original file system. The format
629 of \fItime-last-checked\fR
630 is the international date format, with an optional time specifier, i.e.
631 YYYYMMDD[HH[MM[SS]]]. The keyword \fBnow\fR
632 is also accepted, in which case the last checked time will be set to the
633 current time.
634 .TP
635 .BI \-u " user"
636 Set the user who can use the reserved file system blocks. \fIuser\fR
637 can be a numerical uid or a user name. If a user name is given, it
638 is converted to a numerical uid before it is stored in the superblock.
639 .TP
640 .BI \-U " UUID"
641 Set the universally unique identifier (UUID) of the file system to \fIUUID\fR.
642 The format of the UUID is a series of hex digits separated by hyphens,
643 like this: "c1b9d5a2-f162-11cf-9ece-0020afc76f16".
644 The \fIUUID\fR parameter may also be one of the following:
645 .RS 1.2i
646 .TP
647 .B clear
648 clear the file system UUID
649 .TP
650 .B random
651 generate a new randomly-generated UUID
652 .TP
653 .B time
654 generate a new time-based UUID
655 .RE
656 .IP
657 The UUID may be used by
658 .BR mount (8),
659 .BR fsck (8),
660 and
661 .BR /etc/fstab (5)
662 (and possibly others) by specifying \fBUUID=\fIuuid\fR
663 instead of a block special device name like \fI/dev/hda1\fR.
664 .IP
665 See \fBuuidgen\fR(8) for more information.
666 If the system does not have a good random number generator such as
667 \fI/dev/random\fR or \fI/dev/urandom\fR, \fBtune2fs\fR
668 will automatically use a time-based UUID instead of a randomly-generated UUID.
669 .TP
670 .BI \-z " undo_file"
671 Before overwriting a file system block, write the old contents of the block to
672 an undo file. This undo file can be used with \fBe2undo\fR(8) to restore the old
673 contents of the file system should something go wrong. If the empty string is
674 passed as the \fIundo_file\fR argument, the undo file will be written to a file
675 named tune2fs-\fIdevice\fR.e2undo in the directory specified via the
676 \fBE2FSPROGS_UNDO_DIR\fR environment variable.
677 .sp
678 .B WARNING:
679 The undo file cannot be used to recover from a power or system crash.
680 .SH BUGS
681 We haven't found any bugs yet. That doesn't mean there aren't any...
682 .SH AUTHOR
683 .B tune2fs
684 was written by Remy Card <[email protected]>. It is currently being
685 maintained by Theodore Ts'o <[email protected]>.
686 .B tune2fs
687 uses the ext2fs library written by Theodore Ts'o <[email protected]>.
688 This manual page was written by Christian Kuhtz <[email protected]>.
689 Time-dependent checking was added by Uwe Ohse <[email protected]>.
690 .SH AVAILABILITY
691 .B tune2fs
692 is part of the e2fsprogs package and is available from
693 http://e2fsprogs.sourceforge.net.
694 .SH SEE ALSO
695 .BR debugfs (8),
696 .BR dumpe2fs (8),
697 .BR e2fsck (8),
698 .BR mke2fs (8),
699 .BR ext4 (5)