|
|
|
X11/xfs(1) -- X font server
|
|
Xfs is the X Window System font server. It supplies fonts to X Window System display servers. |
|
xfsdump(1) -- XFS filesystem incremental dump utility
|
|
xfsdump backs up files and their attributes in a filesystem. The files are dumped to storage media, a regular file, or standard output. Options allow the operator to have all files dumped, just files that have changed since a previous dump, or just files contained in a list of pathnames. The xfsrestore(1M) utility re-populates a filesystem with the contents of the dump. Each invocation of xfsdump dumps just one filesystem. That invocation is termed a dump session. The dump session splits the fil... |
|
|
xfsinvutil(1) -- xfsdump inventory database checking and pruning utility
|
|
xfsdump(1M) maintains an online dump inventory in /var/xfsdump/inventory. The -I option of xfsdump displays the inventory contents hierarchically. The levels of the hierarchy are: filesystem, dump session, stream, and media file. Over time, this database may grow too large as xfsdump and xfsrestore(1M) do not remove entries from the inventory. The database may also develop inconsistencies for various reasons such as operator errors etc., that may cause xfsdump or xfsrestore to print error or war... |
|
xfsrestore(1) -- XFS filesystem incremental restore utility
|
|
xfsrestore restores filesystems from dumps produced by xfsdump(1M). Two modes of operation are available: simple and cumulative. The default is simple mode. xfsrestore populates the specified destination directory, dest, with the files contained in the dump media. The -r option specifies the cumulative mode. Successive invocations of xfsrestore are used to apply a chronologically ordered sequence of delta dumps to a base (level 0) dump. The contents of the filesystem at the time each dump was pr... |
|
xfs_bmap(1) -- print block mapping for an XFS file
|
|
xfs_bmap prints the map of disk blocks used by files in an XFS filesystem. The map lists each extent used by the file, as well as regions in the file that do not have any corresponding blocks (holes). Each line of the listings takes the following form: extent: [startoffset..endoffset]: startblock..endblock Holes are marked by replacing the startblock..endblock with hole. All the file offsets and disk blocks are in units of 512-byte blocks, no matter what the filesystem's block size is. If porti... |
|
xfs_check(1) -- check XFS filesystem consistency
|
|
xfs_check checks whether an XFS filesystem is consistent. It is normally run only when there is reason to believe that the filesystem has a consistency problem. The filesystem to be checked is specified by the xfs_special argument, which should be the disk or volume device for the filesystem. Filesystems stored in files can also be checked, using the -f flag. The filesystem should normally be unmounted or read-only during the execution of xfs_check. Otherwise, spurious problems are reported. xfs... |
|
xfs_chver(1) -- change the version of a filesystem to enable the extent unwritten version.
|
|
xfs_chver uses the xfs_db command to change the version of a filesystem to enable the extent unwritten version. This version is needed to close a security hole where a process can sometimes read old data off disk. The command must be run by the super-user. The command either does all devices found in fstab(4) when the -a option is used or the given devices from the second form above. The command either does the changes or creates scripts which can later be applied using the xfs_db command. If th... |
|
xfs_copy(1) -- copy the contents of an XFS filesystem
|
|
xfs_copy copies an XFS filesystem to one or more targets in parallel (see xfs(4)). The first (source) argument must be the pathname of the device or file containing the XFS filesystem. The remaining arguments specify one or more target devices or a filename. If the pathnames specify devices, a copy of the source XFS filesystem is created on each device. If any of the source or target device names specify devices that are not raw devices, xfs_copy attempts to locate the raw device corresponding t... |
|
xfs_db(1) -- debug an XFS filesystem
|
|
xfs_db is used to examine an XFS filesystem. Under rare circumstances it can also be used to modify an XFS filesystem, but that task is normally left to xfs_repair(1M) or to scripts such as xfs_chver that run xfs_db. xfs_db64 is a 64-bit version of xfs_db which is not as susceptible to running out of memory. It is available only on 64-bit capable systems. The options to xfs_db are: -c cmd xfs_db commands may be run interactively (the default) or as arguments on the command line. Multiple -c argu... |
|
xfs_estimate(1) -- estimate the space that an XFS filesystem will take
|
|
For each directory argument, xfs_estimate estimates the space that directory would take if it were copied to an XFS filesystem. xfs_estimate does not cross mount points. The following definitions are used: KB = *1024 MB = *1024*1024 GB = *1024*1024*1024 The xfs_estimate options are: -b blocksize Use blocksize instead of the default blocksize of 4096 bytes. The modifier k can be used after the number to indicate multiplication by 1024. For example, xfs_estimate |
|
xfs_growfs(1) -- expand an XFS filesystem
|
|
xfs_growfs expands an existing XFS filesystem (see xfs(4)). The mount- point argument is the pathname of the directory where the filesystem is mounted. The filesystem must be mounted to be grown (see mount(1M)). The existing contents of the filesystem are undisturbed, and the added space becomes available for additional file storage. The options to xfs_growfs are: -d, -D size Specifies that the data section of the filesystem should be grown. If the -D size option is given, the data section is gr... |
|
xfs_logprint(1) -- print the log of an XFS filesystem
|
|
xfs_logprint prints the log of an XFS filesystem (see xfs(4)). The device-name argument is the pathname of the partition or logical volume containing the filesystem. The contents of the filesystem remain undisturbed. There are two major modes of operation in xfs_logprint. One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The transactional view prints only the portion of the log that pertains to recovery. In other word... |
|
xfs_ncheck(1) -- generate pathnames from i-numbers for XFS
|
|
xfs_ncheck with no -i arguments generates an inode number and pathname list of all files on the given filesystem. Names of directory files are followed by /.. The output is not sorted in any particular order. The filesystem to be examined is specified by the xfs_special argument, which should be the disk or volume device for the filesystem. Filesystems stored in files can also be checked, using the -f flag. xfs_ncheck64 is a 64-bit version of xfs_check which is not as susceptible to running out ... |
|
xfs_repair(1) -- repair an XFS filesystem
|
|
xfs_repair repairs corrupt or damaged XFS filesystems (see xfs(4)). xfs_repair does not work on EFS filesystems (see fsck(1M)). The filesystem is specified using the xfs_special argument which should be the device name of the disk partition or volume containing the filesystem. If given the name of a block device, xfs_repair will attempt to find the raw device associated with the specified block device and will use the raw device instead. Regardless, the filesystem to be repaired must be unmounte... |
|
X11/xfwp(1) -- X firewall proxy
|
|
The X firewall proxy (xfwp) is an application layer gateway proxy that may be run on a network firewall host to forward X traffic across the firewall. Used in conjunction with the X server Security extension and authorization checking, xfwp constitutes a safe, simple, and reliable mechanism both to hide the addresses of X servers located on the Intranet and to enforce a server connection policy. Xfwp cannot protect against mischief originating on the Intranet; however, when properly configured i... |
