Commit ad52f60
committed
nvmeof: treat "connecting" state as valid in path detection
When checking if a path to a gateway already exists,
treat both "live" and "connecting" states as
valid connections that should not be re-attempted.
The "connecting" state indicates the NVMe kernel
is actively trying to establish or re-establish
a connection, which occurs in scenarios like:
- Initial connection establishment
- Gateway temporarily unavailable and kernel retrying
- Subsystem deleted and recreated on the gateway
The kernel's ctrl_loss_tmo mechanism will continue
retry attempts for up to 30 minutes
( by -l param in nvme connect command).
Attempting nvme connect while a path is in
"connecting" state results in "already connected"
errors and can cause volume attachment failures
during create/delete cycles.
By treating "connecting" as a valid state,
we allow the kernel's retry logic to handle
reconnection automatically without interference.
Signed-off-by: gadi-didi <gadi.didi@ibm.com>1 parent 80c0474 commit ad52f60
1 file changed
+16
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
261 | 261 | | |
262 | 262 | | |
263 | 263 | | |
| 264 | + | |
264 | 265 | | |
| 266 | + | |
| 267 | + | |
| 268 | + | |
| 269 | + | |
| 270 | + | |
| 271 | + | |
| 272 | + | |
| 273 | + | |
| 274 | + | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
265 | 279 | | |
266 | 280 | | |
267 | | - | |
| 281 | + | |
| 282 | + | |
268 | 283 | | |
269 | 284 | | |
270 | 285 | | |
| |||
0 commit comments