Manual pages: raw.8: Minor formatting and wording fixes

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
This commit is contained in:
Michael Kerrisk (man-pages) 2020-07-24 12:06:09 +02:00 committed by Karel Zak
parent 342af74630
commit 8be2cc8171
1 changed files with 10 additions and 7 deletions

View File

@ -34,10 +34,10 @@ device numbers, or as a path name
to an existing block device file.
.PP
The bindings already in existence can be queried with the
.I \-q
.B \-q
option, which is used either with a raw device filename to query that one
device, or with the
.I \-a
.B \-a
option to query all bound raw devices.
.PP
Unbinding can be done by specifying major and minor 0.
@ -66,8 +66,8 @@ will query an existing binding instead of setting a new one.
.TP
\fB\-a\fR, \fB\-\-all\fR
With
.B \-q
, specify that all bound raw devices should be queried.
.BR \-q ,
specify that all bound raw devices should be queried.
.TP
\fB\-h\fR, \fB\-\-help\fR
Display help text and exit.
@ -78,20 +78,23 @@ Display version information and exit.
.SH NOTES
Rather than using raw devices applications should prefer
.BR open (2)
devices, such as /dev/sda1, with the O_DIRECT flag.
devices, such as
.IR /dev/sda1 ,
with the
.B O_DIRECT
flag.
.SH BUGS
The Linux
.BR dd (1)
command should be used without the \fBbs=\fR option, or the blocksize
needs to be a multiple of the sector size of the device (512 bytes usually),
otherwise it will fail with "Invalid Argument" messages (EINVAL).
.PP
Raw I/O devices do not maintain cache coherency with the Linux block
device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the
contents of the actual storage device underneath. This is deliberate,
but is regarded either a bug or a feature depending on who you ask!
but is regarded as either a bug or a feature, depending on who you ask!
.SH AUTHORS
Stephen Tweedie (sct@redhat.com)
.SH AVAILABILITY