From 860ce480723c00552f97709a03c37a319601bedc Mon Sep 17 00:00:00 2001 From: Gleb Chesnokov Date: Thu, 20 Aug 2026 16:11:14 +0300 Subject: [PATCH] docs: Warn about destructive performance tests README.performance runs fio against a block device, exports LUNs, logs in iSCSI sessions and may enable multipath. Its placeholders look copyable, but using the wrong path or host can overwrite storage and change both target and initiator state. Put an explicit safety boundary before the first command. Require authorization for the exact hosts, transports and configuration, and allow the workflow only with verified disposable backing devices. --- README.performance | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.performance b/README.performance index 7a41d64dc..a32d98a7d 100644 --- a/README.performance +++ b/README.performance @@ -5,6 +5,11 @@ A question that is asked often is how to tune performance. This means how to improve the IOPS and/or bandwidth measured at the initiator side. In this README it is explained how to optimize storage performance. +WARNING: The examples below issue direct I/O, create and export LUNs, create +initiator sessions and may activate multipath. Run them only with explicit +authorization for the target and initiator hosts, transports, configuration +and disposable backing devices. Verify every placeholder before use. + Local storage ------------- Start with measuring the performance of the local block device(s). IOPS can be