Lines Matching full:file

36 .Nd mount file systems
61 device or the remote node (rhost:path) on to the file system tree at the point
69 file.
71 The system maintains a list of currently mounted file systems.
86 All the file systems described in
99 root file system which is always remounted to preserve
112 file to use.
115 a file system mount status from read-write to read-only.
117 forces the R/W mount of an unclean file system (dangerous; use with
124 those file systems which are marked as
129 option, also mount those file systems which are marked as
152 All I/O to the file system should be done asynchronously.
155 flag to set, since it does not guarantee that the file system structure
162 Update the file access time when reading from a file.
165 This flag indicates that the file system was mounted by
167 Automounted file systems are automatically unmounted by
170 Mount the file system read-write.
172 then automatically try to mount the file system read-only.
177 the mounted file system.
184 a file system mount status from read-write to read-only.
186 forces the R/W mount of an unclean file system (dangerous; use with caution).
192 file for the file system.
194 This file system should be skipped when
204 to use the specified program to mount the file system, instead of calling
212 Enable multi-label Mandatory Access Control, or MAC, on the specified file
214 If the file system supports multilabel operation, individual labels will
215 be maintained for each object in the file system, rather than using a
239 Do not update the file access time when reading from a file.
241 is useful on file systems where there are large numbers of files and
242 performance is more critical than updating the file access time (which is
244 This option is currently only supported on local file systems.
246 This file system should be skipped when
259 Do not allow execution of any binaries on the mounted file system.
260 This option is useful for a server that has file systems containing
274 on the mounted file system.
288 Snapshot files must be created in the file system that is being
290 You may create up to 20 snapshots per file system.
303 clear the schg flag before removing a snapshot file.
312 on the snapshot file.
313 Assuming that the file system was clean when it was mounted, you should always
321 You will get a dump that is consistent with the file system as of the timestamp
325 Mount the snapshot as a frozen image of the file system.
335 file system at
348 A directory on the mounted file system will respond to the SUID bit
353 the file, and it will not be given to root.
361 Only UFS file systems support this option.
366 All I/O to the file system should be done synchronously.
370 indicate that the status of an already mounted file system should be changed.
373 of the mounted file system root and the existing directory.
374 Lookups will be done in the mounted file system first.
375 If those operations fail due to a non-existent file the underlying
377 All creates are done in the mounted file system.
379 The file system is untrusted and the kernel should use more
380 extensive checks on the file-system's metadata before using it.
381 This option is intended to be used when mounting file systems
386 Any additional options specific to a file system type that is not
417 Additional options specific to file system types
433 The file system is to be mounted read-only.
434 Mount the file system read-only (even the super-user may not write it).
443 is used to indicate the file system type.
451 file systems of the specified type.
453 The list of file system types can be prefixed with
455 to specify the file system types for which action should
465 mounts all file systems except those of type NFS and NULLFS.
477 However, for the following file system types:
494 is replaced by the file system type name.
497 file systems are mounted by the program
500 Most file systems will be dynamically loaded by the kernel
505 flag indicates that the status of an already mounted file
511 also a file system can be changed from read-only to read-write
514 files on the file system are currently open for writing unless the
529 is used alone, show all file systems, including those that were mounted with the
531 flag and show additional information about each file system (including fsid
534 The file system object is to be read and write.
541 is set, all operations are performed against the specified file.
553 file system table
562 .Dl XXXXX file system is not available
564 The kernel does not support the respective file system type.
566 support for a particular file system might be provided either on a static
611 is accessible from the mounted file system.
618 is preferred over the use of the file system specific
626 only when the file system is mounted via
629 It is possible for a corrupted file system to cause a crash.