pldd.1, bpf.2, chdir.2, clone.2, fanotify_init.2, fanotify_mark.2, intro.2, ipc.2...

[thirdparty/man-pages.git] / man2 / mount.2

diff --git a/man2/mount.2 b/man2/mount.2
index efc4427814d735f6c7758f7becb949e5b28dcd1c..cf36ebc9ba5d3375243e9bcdc4a9b28324b6f963 100644 (file)
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -37,7 +37,7 @@
 .\" 2008-10-06, mtk: move umount*() material into separate umount.2 page.
 .\" 2008-10-06, mtk: Add discussion of namespaces.
 .\"
-.TH MOUNT 2 2018-02-02 "Linux" "Linux Programmer's Manual"
+.TH MOUNT 2 2019-08-02 "Linux" "Linux Programmer's Manual"
 .SH NAME
 mount \- mount filesystem
 .SH SYNOPSIS
@@ -309,7 +309,7 @@ The following flags are per-superblock:
 and
 .BR MS_SYNCHRONOUS .
 .\" And MS_I_VERSION?
-The inital settings of these flags are determined on the first
+The initial settings of these flags are determined on the first
 mount of the filesystem, and will be shared by all subsequent mounts
 of the same filesystem.
 Subsequently, the settings of the flags can be changed
@@ -410,7 +410,7 @@ then the remount operation preserves the existing values of these flags
 .BR MS_RELATIME ).
 .PP
 Since Linux 2.6.26, the
-.B MS_RMOUNT
+.B MS_REMOUNT
 flag can be used with
 .B MS_BIND
 to modify only the per-mount-point flags.
@@ -543,7 +543,7 @@ with the
 and
 .BR MS_REC
 flags) is performed on a directory subtree,
-any bind mounts within the subtree are automatically pruned
+any unbindable mounts within the subtree are automatically pruned
 (i.e., not replicated)
 when replicating that subtree to produce the target subtree.
 .PP
@@ -632,6 +632,19 @@ A component of a path was not searchable.
 Mounting a read-only filesystem was attempted without giving the
 .B MS_RDONLY
 flag.
+.IP
+The file system may be read-only for various reasons, including:
+it resides on a read-only optical disk;
+it is resides on a device with a physical switch that has been set to
+mark the device read-only;
+the filesystem implementation was compiled with read-only support;
+or errors were detected when initially mounting the filesystem,
+so that it was marked read-only
+and can't be remounted as read-write (until the errors are fixed).
+.IP
+Some filesystems instead return the error
+.BR EROFS
+on an attempt to mount a read-only filesystem.
 .TP
 .B EACCES
 The block device
@@ -673,6 +686,24 @@ was not already mounted on
 .B EINVAL
 A move operation
 .RB ( MS_MOVE )
+was attempted, but the mount tree under
+.I source
+includes unbindable mounts and
+.I target
+is a mount point that has propagation type
+.BR MS_SHARED .
+.TP
+.B EINVAL
+A move operation
+.RB ( MS_MOVE )
+was attempted, but the parent mount of
+.I source
+mount has propagation type
+.BR MS_SHARED .
+.TP
+.B EINVAL
+A move operation
+.RB ( MS_MOVE )
 was attempted, but
 .I source
 was not a mount point, or was \(aq/\(aq.
@@ -757,6 +788,14 @@ is out of range.
 .TP
 .B EPERM
 The caller does not have the required privileges.
+.TP
+.B EROFS
+Mounting a read-only filesystem was attempted without giving the
+.B MS_RDONLY
+flag.
+See
+.BR EACCES ,
+above.
 .SH VERSIONS
 The definitions of
 .BR MS_DIRSYNC ,
@@ -864,7 +903,9 @@ and
 for details of these files.
 .SH SEE ALSO
 .BR mountpoint (1),
+.BR chroot (2),
 .BR ioctl_iflags (2),
+.BR pivot_root (2),
 .BR umount (2),
 .BR mount_namespaces (7),
 .BR path_resolution (7),