From 643abf302db1fac21234d61f8f0a8e1753766ad2 Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sat, 18 Apr 2015 19:38:07 +0200 Subject: [PATCH 147/325] gmountver.8: Note that GEOM mount verification has dangerous bugs Obtained from: ElectroBSD --- lib/geom/mountver/gmountver.8 | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/lib/geom/mountver/gmountver.8 b/lib/geom/mountver/gmountver.8 index 4c27a652b0b0..ddb9e2b2a73f 100644 --- a/lib/geom/mountver/gmountver.8 +++ b/lib/geom/mountver/gmountver.8 @@ -61,6 +61,8 @@ got disconnected - it queues all the I/O requests and waits for the provider to reappear. When that happens, it attaches to it and sends the queued requests. .Pp +At least that's the theory, please note the BUGS section. +.Pp The first argument to .Nm indicates an action to be performed: @@ -119,6 +121,13 @@ If set to 0, .Nm will reattach to the device even if the device reports a different disk ID. .El +.Sh BUGS +The mount verification GEOM class can stall all the disk I/O instead +of just the device it is configured for. +The disk identification check currently has to be turned off for the class +to actually attach reappearing providers. +Obviously this is dangerous. +.El .Sh EXIT STATUS Exit status is 0 on success, and 1 if the command fails. .Sh SEE ALSO -- 2.32.0