You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature would like to see added to OpenZFS
During a slow pool import, a number of zpool commands can hang until the slow import is completed, with zero feedback to indicate that this is the case.
If possible, I would like to see messages added to indicate why the command is hanging, e.g- "Operation delayed due to import(s): pool1, pool2". And if possible, to indicate the progress of any relevant operation.
For example, if a pool is slow to import because ZFS is running through part of the event log, completing interrupted deletions etc., then it would be great if a percentage could be given (if such a figure is possible to get).
How will this feature improve OpenZFS?
It will make it immediately clear why an operation is stalled, at least in common cases that support is added for. Imports and exports are the big ones I'm aware of, this can stall nearly all zpool commands until they are complete.
Additional context
I recently suffered a power loss (and that discovered my UPS is useless, hooray!) while I had a large write stuck in RAM, so when I was able to start back up again the import took nearly 15 minutes as ZFS presumably had to release everything incomplete that had been written, plus whatever other checks it goes through when interrupted.
But as far as I could tell there was no way to get any feedback about this, as zpool commands just hanged until the import was complete, including importing other pools (though that's on me, I should have known one of the other pools would be fine since it was barely doing anything at the time, and imported that one first).
Of course removing the deadlocks might be nice long term, but I don't know how feasible this is, but if it's possible to spit out even a basic message I think it would help to make clear when a hang is "normal" (or at least expected), and if any more information can be given that'd be fantastic.
The text was updated successfully, but these errors were encountered:
It's not specifically what you asked for, but #15539 added more info about what import is up to. It's available in dbgmsg and the import_progress kstat.
It's not specifically what you asked for, but #15539 added more info about what import is up to. It's available in dbgmsg and the import_progress kstat.
Oh I didn't know about that, that's handy the information is available at least.
In that case just a generic message should suffice if an import is in progress, since the message can simply direct a user to the import_progress kstat (or a wiki article about it) if they want more information? This would help with discoverability at least as I had no idea that existed.
Describe the feature would like to see added to OpenZFS
During a slow pool import, a number of
zpool
commands can hang until the slow import is completed, with zero feedback to indicate that this is the case.If possible, I would like to see messages added to indicate why the command is hanging, e.g- "Operation delayed due to import(s): pool1, pool2". And if possible, to indicate the progress of any relevant operation.
For example, if a pool is slow to import because ZFS is running through part of the event log, completing interrupted deletions etc., then it would be great if a percentage could be given (if such a figure is possible to get).
How will this feature improve OpenZFS?
It will make it immediately clear why an operation is stalled, at least in common cases that support is added for. Imports and exports are the big ones I'm aware of, this can stall nearly all
zpool
commands until they are complete.Additional context
I recently suffered a power loss (and that discovered my UPS is useless, hooray!) while I had a large write stuck in RAM, so when I was able to start back up again the import took nearly 15 minutes as ZFS presumably had to release everything incomplete that had been written, plus whatever other checks it goes through when interrupted.
But as far as I could tell there was no way to get any feedback about this, as
zpool
commands just hanged until the import was complete, including importing other pools (though that's on me, I should have known one of the other pools would be fine since it was barely doing anything at the time, and imported that one first).Of course removing the deadlocks might be nice long term, but I don't know how feasible this is, but if it's possible to spit out even a basic message I think it would help to make clear when a hang is "normal" (or at least expected), and if any more information can be given that'd be fantastic.
The text was updated successfully, but these errors were encountered: