Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
tune2fs(8)
Edit
PageHistory
Diff
Info
LikePages
TUNE2FS !!!TUNE2FS NAME SYNOPSIS DESCRIPTION OPTIONS BUGS AUTHOR AVAILABILITY SEE ALSO ---- !!NAME tune2fs - adjust tunable filesystem parameters on second extended filesystems !!SYNOPSIS __tune2fs__ [[ __-l__ ] [[ __-c__ ''max-mount-counts'' ] [[ __-e__ ''errors-behavior'' ] [[ __-f__ ] [[ __-i__ ''interval-between-checks'' ] [[ __-j__ ] [[ __-J__ ''journal-options'' ] [[ __-m__ ''reserved-blocks-percentage'' ] [[ __-r__ ''reserved-blocks-count'' ] [[ __-s__ ''sparse-super-flag'' ] [[ __-u__ ''user'' ] [[ __-g__ ''group'' ] [[ __-C__ ''mount-count'' ] [[ __-L__ ''volume-name'' ] [[ __-M__ ''last-mounted-directory'' ] [[ __-O__ [[^]''feature''[[,...] ] [[ __-T__ ''time-last-checked'' ] [[ __-U__ ''UUID'' ] device !!DESCRIPTION __tune2fs__ adjusts tunable filesystem parameters on a Linux second extended filesystem. !!OPTIONS __-c__ ''max-mount-counts'' Adjust the maximal mounts count between two filesystem checks. If ''max-mount-counts'' is 0 then the number of times the filesystem is mounted will be disregarded by e2fsck(8) and the kernel. Staggering the mount-counts at which filesystems are forcibly checked will avoid all filesystems being checked at one time when using journaled filesystems. You should strongly consider the consequences of disabling mount-count-dependent checking entirely. Bad disk drives, cables, memory, and kernel bugs could all corrupt a filesystem without marking the filesystem dirty or in error. If you are using journaling on your filesystem, your filesystem will __never__ be marked dirty, so it will not normally be checked. A filesystem error detected by the kernel will still force an fsck on the next reboot, but it may already be too late to prevent data loss at that point. See also the __-i__ option for time-dependent checking. __-C__ ''mount-count'' Set the number of times the filesystem has been mounted. Can be used in conjunction with -c to force an fsck on the filesystem at the next reboot. __-e__ ''error-behavior'' Change the behavior of the kernel code when errors are detected. In all cases, a filesystem error will cause e2fsck(8) to check the filesystem on the next boot. ''error-behavior'' can be one of the following: __continue__ Continue normal execution. __remount-ro__ Remount filesystem read-only. __panic__ Cause a kernel panic. __-f__ Force the tune2fs operation to complete even in the face of errors. This option is useful when removing the __has_journal__ filesystem feature from a filesystem which has an external journal (or is corrupted such that it appears to have an external journal), but that external journal is not available. __WARNING:__ Removing an external journal from a filesystem which was not cleanly unmounted without first replaying the external journal can result in severe data loss and filesystem corruption. __-g__ ''group'' Set the group which can use reserved filesystem blocks. The ''group'' parameter can be a numerical gid or a group name. If a group name is given, it is converted to a numerical gid before it is stored in the superblock. __-i__ ''interval-between-checks''[[__d__|__m__|__w__] Adjust the maximal time between two filesystem checks. No postfix or __d__ result in days, __m__ in months, and __w__ in weeks. A value of zero will disable the time-dependent checking. It is strongly recommended that either __-c__ (mount-count-dependent) or __-i__ (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to filesystem corruption due to bad disks, cables, memory, or kernel bugs to go unnoticed until they cause data loss or corruption. __-j__ Add an ext3 journal to the filesystem. If the __-J__ option is not specified, the default journal parameters will be used to create an appropriately sized journal (given the size of the filesystem) stored within the filesystem. Note that you must be using a kernel which has ext3 support in order to actually make use of the journal. __-J__ journal-options Override the default ext3 journal parameters. Journal options are comma separated, and may take an argument using the equals ('=') sign. The following journal options are supported: __size=__''journal-size'' Create a journal stored in the filesystem of size ''journal-size'' megabytes. The size of the journal must be at least 1024 filesystem blocks (i.e., 1MB if using 1k blocks, 4MB if using 4k blocks, etc.) and may be no more than 102,400 filesystem blocks. There must be enough free space in the filesystem to create a journal of that size. __device=__''external-journal'' Attach the filesystem to the journal block device located on ''external-journal''. The external journal must have been already created using the command __mke2fs -O journal_dev__ ''external-journal'' Note that ''external-journal'' must be formatted with the same block size as filesystems which will be using it. Instead of specifying a device name directly, ''external-journal'' can also be specified by either __LABEL=__''label'' or __UUID=__''UUID'' to locate the external journal by either the volume label or UUID stored in the ext2 superblock at the start of the journal. Use dumpe2fs(8) to display a journal device's volume label and UUID. See also the __-L__ option of tune2fs(8). Only one of the __size__ or __device__ options can be given for a filesystem. __-l__ List the contents of the filesystem superblock. __-L__ ''volume-label'' Set the volume label of the filesystem. Ext2 filesystem labels can be at most 16 characters long; if ''volume-label'' is longer than 16 characters, __tune2fs__ will truncate it and print a warning. The volume label can be used by mount(8), fsck(8), and /etc/fstab(5) (and possibly others) by specifying __LABEL=__''volume_label'' instead of a block special device name like __/dev/hda5__. __-m__ ''reserved-blocks-percentage'' Set the percentage of reserved filesystem blocks. __-M__ ''last-mounted-directory'' Set the last-mounted directory for the filesystem. __-O__ [[^]''feature''[[,...] Set or clear the indicated filesystem features (options) in the filesystem. More than one filesystem feature can be cleared or set by separating features with commas. Filesystem features prefixed with a caret character ('^') will be cleared in the filesystem's superblock; filesystem features without a prefix character or prefixed with a plus character ('+') will be added to the filesystem. The following filesystem features can be set or cleared using __tune2fs__: __sparse_super__ Limit the number of backup superblocks to save space on large filesystems. __filetype__ Store file type information in directory entries. __has_journal__ Create an ext3 journal (as if using the __-j__ option). After setting or clearing __sparse_super__ and __filetype__ filesystem features, e2fsck(8) must be run on the filesystem to return the filesystem to a consistent state. __Tune2fs__ will print a message requesting that the system administrator run e2fsck(8) if necessary. __Warning:__ Linux kernels before 2.0.39 and many 2.1 series kernels do not support the filesystems that use any of these features. Enabling certain filesystem features may prevent the filesystem from being mounted by kernels which do not support those features. __-r__ ''reserved-blocks-count'' Set the number of reserved filesystem blocks. __-s__ [[__0__|__1__] Turn the sparse super feature off or on. Turning this feature on saves space on really big filesystems. This is the same as using the __-O sparse_super__ option. __Warning:__ Linux kernels before 2.0.39 do not support this feature. Neither do all Linux 2.1 kernels; please don't use this unless you know what you're doing! You need to run e2fsck(8) on the filesystem after changing this feature in order to have a valid filesystem. __-T__ ''time-last-checked'' Set the time the filesystem was last checked using __e2fsck__. This can be useful in scripts which use a Logical Volume Manager to make a consistent snapshot of a filesystem, and then check the filesystem during off hours to make sure it hasn't been corrupted due to hardware problems, etc. If the filesystem was clean, then this option can be used to set the last checked time on the original filesystem. The format of ''time-last-checked'' is the international date format, with an optional time specifier, i.e. YYYYMMDD[[[[HHMM]SS]. The keyword __now__ is also accepted, in which case the last checked time will be set to the current time. __-u__ ''user'' Set the user who can use the reserved filesystem blocks. ''user'' can be a numerical uid or a user name. If a user name is given, it is converted to a numerical uid before it is stored in the superblock. __-U__ ''UUID'' Set the universally unique identifier (UUID) of the filesystem to ''UUID''. The format of the UUID is a series of hex digits separated by hypthens, like this: ''UUID'' parameter may also be one of the following: ''clear'' clear the filesystem UUID ''random'' generate a new randomly-generated UUID ''time'' generate a new time-based UUID The UUID may be used by mount(8), fsck(8), and /etc/fstab(5) (and possibly others) by specifying __UUID=__''uuid'' instead of a block special device name like __/dev/hda1__. See uuidgen(8) for more information. If the system does not have a good random number generator such as ''/dev/random'' or ''/dev/urandom'', __tune2fs__ will automatically use a time-based UUID instead of a randomly-generated UUID. !!BUGS We haven't found any bugs yet. That doesn't mean there aren't any... !!AUTHOR __tune2fs__ was written by Remy Card __tune2fs__ uses the ext2fs library written by Theodore Ts'o __ !!AVAILABILITY __tune2fs__ is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net. !!SEE ALSO dumpe2fs(8), __e2fsck__(8), mke2fs(8) ----
10 pages link to
tune2fs(8)
:
ENOSPC
mke2fs(8)
mkfs.ext2(8)
mkfs.ext3(8)
Man8t
fsck.ext3(8)
dumpe2fs(8)
e2label(8)
mount(8)
Ext3
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
