mount.2: Document EROFS for read-only filesystems

See https://bugzilla.kernel.org/show_bug.cgi?id=200649

Reported-by: Harry Mallon <hjmallon@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk 2018-11-05 10:15:23 +01:00
parent ed6d190860
commit 1c1ccb2c65
1 changed files with 12 additions and 0 deletions

View File

@ -641,6 +641,10 @@ 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
@ -766,6 +770,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 ,