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
It would be great if we could skip reading metaslab-related data when importing the pool readonly.
The main reason for having such feature would be to help in recovery of data in failure scenarios where space-accounting and its relevant on-disk state have been corrupted but we still want to access the pool's data.
The text was updated successfully, but these errors were encountered:
I thought this was already the case, for exactly the reason you mentioned. But looking at the git history it appears we made a change along these lines 7fc8c33, but reverted it afe3732 due to some ztest failures (which I'm sure can be fixed). As part of this, we should make sure to add a test case for this since it would be easily to accidentally break this an not notice.
The only zdb utility require to read metaslab-related data during
read-only pool import because of spacemaps validation. Add global
varialbe which will allow zdb read spacemaps in case of readonly
import mode.
Signed-off-by: Fedor Uporov <[email protected]>
Closesopenzfs#9095
The only zdb utility require to read metaslab-related data during
read-only pool import because of spacemaps validation. Add global
variable which will allow zdb read spacemaps in case of readonly
import mode.
Reviewed-by: Serapheim Dimitropoulos <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Fedor Uporov <[email protected]>
Closesopenzfs#9095Closesopenzfs#12687
The only zdb utility require to read metaslab-related data during
read-only pool import because of spacemaps validation. Add global
variable which will allow zdb read spacemaps in case of readonly
import mode.
Reviewed-by: Serapheim Dimitropoulos <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Fedor Uporov <[email protected]>
Closes#9095Closes#12687
It would be great if we could skip reading metaslab-related data when importing the pool readonly.
The main reason for having such feature would be to help in recovery of data in failure scenarios where space-accounting and its relevant on-disk state have been corrupted but we still want to access the pool's data.
The text was updated successfully, but these errors were encountered: