mirror of https://github.com/mkerrisk/man-pages
mount.2: EACCES: note some reasons why a filesystem may be read-only
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
642df17c43
commit
ed6d190860
|
@ -632,6 +632,15 @@ 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).
|
||||
.TP
|
||||
.B EACCES
|
||||
The block device
|
||||
|
|
Loading…
Reference in New Issue