== NAME
-fsck.cramfs - fsck compressed ROM file system
+fsck.cramfs - fsck compressed ROM filesystem
== SYNOPSIS
== DESCRIPTION
-*fsck.cramfs* is used to check the cramfs file system.
+*fsck.cramfs* is used to check the cramfs filesystem.
== OPTIONS
Use this blocksize, defaults to page size. Must be equal to what was set at creation time. Only used for *--extract*.
*--extract*[**=**_directory_]::
-Test to uncompress the whole file system. Optionally extract contents of the _file_ to _directory_.
+Test to uncompress the whole filesystem. Optionally extract contents of the _file_ to _directory_.
*-a*::
This option is silently ignored.
*0*::
success
*4*::
-file system was left uncorrected
+filesystem was left uncorrected
*8*::
operation error, such as unable to allocate memory
*16*::
== NAME
-mkfs.cramfs - make compressed ROM file system
+mkfs.cramfs - make compressed ROM filesystem
== SYNOPSIS
== DESCRIPTION
-Files on cramfs file systems are zlib-compressed one page at a time to allow random read access. The metadata is not compressed, but is expressed in a terse representation that is more space-efficient than conventional file systems.
+Files on cramfs filesystems are zlib-compressed one page at a time to allow random read access. The metadata is not compressed, but is expressed in a terse representation that is more space-efficient than conventional filesystems.
-The file system is intentionally read-only to simplify its design; random write access for compressed files is difficult to implement. cramfs ships with a utility (*mkcramfs*(8)) to pack files into new cramfs images.
+The filesystem is intentionally read-only to simplify its design; random write access for compressed files is difficult to implement. cramfs ships with a utility (*mkcramfs*(8)) to pack files into new cramfs images.
File sizes are limited to less than 16 MB.
-Maximum file system size is a little under 272 MB. (The last file on the file system must begin before the 256 MB block, but can extend past it.)
+Maximum filesystem size is a little under 272 MB. (The last file on the filesystem must begin before the 256 MB block, but can extend past it.)
== ARGUMENTS
The _directory_ is simply the root of the directory tree that we want to generate a compressed filesystem out of.
-The _file_ will contain the cram file system, which later can be mounted.
+The _file_ will contain the cram filesystem, which later can be mounted.
== OPTIONS
Use defined block size, which has to be divisible by page size.
*-e* _edition_::
-Use defined file system edition number in superblock.
+Use defined filesystem edition number in superblock.
*-N* *big*|*little*|*host*::
Use the specified endianness. The default is *host*.
*-i* _file_::
-Insert a _file_ to cramfs file system.
+Insert a _file_ to cramfs filesystem.
*-n* _name_::
-Set name of the cramfs file system.
+Set name of the cramfs filesystem.
*-p*::
Pad by 512 bytes for boot code.
The device may be a block device or an image file of one, but this is not enforced. Expect not much fun on a character device :-).
-The _size-in-blocks_ parameter is the desired size of the file system, in blocks. It is present only for backwards compatibility. If omitted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.
+The _size-in-blocks_ parameter is the desired size of the filesystem, in blocks. It is present only for backwards compatibility. If omitted the size will be determined automatically. Only block counts strictly greater than 10 and strictly less than 65536 are allowed.
== OPTIONS
Check the device for bad blocks before creating the filesystem. If any are found, the count is printed.
*-n*, *--namelength* _length_::
-Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for file system versions 1 and 2. Version 3 allows only value 60. The default is 30.
+Specify the maximum length of filenames. Currently, the only allowable values are 14 and 30 for filesystem versions 1 and 2. Version 3 allows only value 60. The default is 30.
*--lock*[**=**_mode_]::
Use an exclusive BSD lock for the device or file that is operated upon.
== TAGS
-All available tags are listed below. Not all tags are supported for all file systems. To enable a tag, set one of the following flags with *blkid_probe_set_superblocks_flags*():
+All available tags are listed below. Not all tags are supported for all filesystems. To enable a tag, set one of the following flags with *blkid_probe_set_superblocks_flags*():
BLKID_SUBLKS_TYPE::
- FSLASTBLOCK - last fsblock/total number of fsblocks
-- FSBLOCKSIZE - file system block size
+- FSBLOCKSIZE - filesystem block size
The following tags are always enabled::
-- BLOCK_SIZE - minimal block size accessible by file system
+- BLOCK_SIZE - minimal block size accessible by filesystem
- MOUNT - cluster mount name (ocfs only)
Command of the process opening the file.
DELETED <``boolean``>::
-Reachability from the file system.
+Reachability from the filesystem.
DEV <``string``>::
ID of the device containing the file.
____
Note that `(deleted)` markers are removed from this column.
Refer to _KNAME_, _DELETED_, or _XMODE_ to know the
-readability of the file from the file system.
+readability of the file from the filesystem.
____
NETLINK.GROUPS <``number``>::
mapped for executing the code. This is also in _MODE_.
+
[-D]:::
-deleted from the file system. See also _DELETED_.
+deleted from the filesystem. See also _DELETED_.
+
[-Ll]:::
locked or leased. _l_ represents a read, a shared lock or a read lease.
*flock* does not detect deadlock. See *flock*(2) for details.
-Some file systems (e. g. NFS and CIFS) have a limited implementation of *flock*(2) and flock may always fail. For details see *flock*(2), *nfs*(5) and *mount.cifs*(8). Depending on mount options, flock can always fail there.
+Some filesystems (e. g. NFS and CIFS) have a limited implementation of *flock*(2) and flock may always fail. For details see *flock*(2), *nfs*(5) and *mount.cifs*(8). Depending on mount options, flock can always fail there.
== EXAMPLES
See *mount*(8), *blkid*(8) or *lsblk*(8) for more details about device identifiers.
-Note that *mount*(8) uses UUIDs as strings. The string representation of the UUID should be based on lower case characters. But when specifying the volume ID of FAT or NTFS file systems upper case characters are used (e.g UUID="A40D-85E7" or UUID="61DB7756DB7779B3").
+Note that *mount*(8) uses UUIDs as strings. The string representation of the UUID should be based on lower case characters. But when specifying the volume ID of FAT or NTFS filesystems upper case characters are used (e.g UUID="A40D-85E7" or UUID="61DB7756DB7779B3").
=== The second field (_fs_file_).
*fstrim* will report the same potential discard bytes each time, but only sectors which had been written to between the discards would actually be discarded by the storage device. Further, the kernel block layer reserves the right to adjust the discard ranges to fit raid stripe geometry, non-trim capable devices in a LVM setup, etc. These reductions would not be reflected in fstrim_range.len (the *--length* option).
*--quiet-unsupported*::
-Suppress error messages if trim operation (ioctl) is unsupported. This option is meant to be used in *systemd* service file or in *cron*(8) scripts to hide warnings that are result of known problems, such as NTFS driver reporting _Bad file descriptor_ when device is mounted read-only, or lack of file system support for ioctl _FITRIM_ call. This option also cleans exit status when unsupported filesystem specified on *fstrim* command line.
+Suppress error messages if trim operation (ioctl) is unsupported. This option is meant to be used in *systemd* service file or in *cron*(8) scripts to hide warnings that are result of known problems, such as NTFS driver reporting _Bad file descriptor_ when device is mounted read-only, or lack of filesystem support for ioctl _FITRIM_ call. This option also cleans exit status when unsupported filesystem specified on *fstrim* command line.
include::man-common/help-version.adoc[]
+
When used in a startup script, making the *--hctosys* function the first caller of *settimeofday*(2) from boot, it will set the NTP '11 minute mode' timescale via the _persistent_clock_is_local_ kernel variable. If the Hardware Clock's timescale configuration is changed then a reboot is required to inform the kernel. See the discussion below, under *Automatic Hardware Clock Synchronization by the Kernel*.
+
-This is a good function to use in one of the system startup scripts before the file systems are mounted read/write.
+This is a good function to use in one of the system startup scripts before the filesystems are mounted read/write.
+
This function should never be used on a running system. Jumping system time will cause problems, such as corrupted filesystem timestamps. Also, if something has changed the Hardware Clock, like NTP's '11 minute mode', then *--hctosys* will set the time incorrectly by including drift compensation.
+
=== Mount options for msdos
-See mount options for fat. If the _msdos_ filesystem detects an inconsistency, it reports an error and sets the file system read-only. The filesystem can be made writable again by remounting it.
+See mount options for fat. If the _msdos_ filesystem detects an inconsistency, it reports an error and sets the filesystem read-only. The filesystem can be made writable again by remounting it.
=== Mount options for ncpfs
== DESCRIPTION
-*pivot_root* moves the root file system of the current process to the directory _put_old_ and makes _new_root_ the new root file system. Since *pivot_root*(8) simply calls *pivot_root*(2), we refer to the man page of the latter for further details.
+*pivot_root* moves the root filesystem of the current process to the directory _put_old_ and makes _new_root_ the new root filesystem. Since *pivot_root*(8) simply calls *pivot_root*(2), we refer to the man page of the latter for further details.
Note that, depending on the implementation of *pivot_root*, root and current working directory of the caller may or may not change. The following is a sequence for invoking *pivot_root* that works in either case, assuming that *pivot_root* and *chroot* are in the current *PATH*:
Note that *chroot* must be available under the old root and under the new root, because *pivot_root* may or may not have implicitly changed the root directory of the shell.
-Note that *exec chroot* changes the running executable, which is necessary if the old root directory should be unmounted afterwards. Also note that standard input, output, and error may still point to a device on the old root file system, keeping it busy. They can easily be changed when invoking *chroot* (see below; note the absence of leading slashes to make it work whether *pivot_root* has changed the shell's root or not).
+Note that *exec chroot* changes the running executable, which is necessary if the old root directory should be unmounted afterwards. Also note that standard input, output, and error may still point to a device on the old root filesystem, keeping it busy. They can easily be changed when invoking *chroot* (see below; note the absence of leading slashes to make it work whether *pivot_root* has changed the shell's root or not).
== OPTIONS
== EXAMPLE
-Change the root file system to _/dev/hda1_ from an interactive shell:
+Change the root filesystem to _/dev/hda1_ from an interactive shell:
....
mount /dev/hda1 /new-root
umount /old-root
....
-Mount the new root file system over NFS from 10.0.0.1:/my_root and run *init*:
+Mount the new root filesystem over NFS from 10.0.0.1:/my_root and run *init*:
....
ifconfig lo 127.0.0.1 up # for portmap
projects / thirdparty / util-linux.git / commitdiff
