-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove corrupt/missing sectors #85
Comments
Added support for removing lost/corrupt sectors during force remove in #318 |
Can I make a request associated to this? I can create a separate ticket if you prefer. I occassionally have concerns about data integrity on certain volumes, it would be nice to be able to check all contracts that have data on that volume. I guess this would not be as useful if there is automated integrity checks, but I'm not sure where development plans are on that. Oh and thank you so much for this work! |
Description
Extends
hostd
's data integrity functionality allowing early detection and notification of corrupt/missing sectors.Missing sectors are sectors whose volume is not currently loaded. This should be considered "temporary," as the volume may become available later. The missing sector references should be permanently removed if the volume is later forcibly removed. Corrupt sectors are sectors whose data does not match the expected sector root. This shouldn't happen during regular operation but is possible if a disk malfunctions. References to corrupt sectors should be removed as soon as they are detected, enabling the sector to be reuploaded and repaired.
When a volume is removed, sectors are migrated to a new volume. If the sector is missing or corrupt, removal is immediately stopped. However, when a volume is "force" removed, the integrity check is ignored and references to missing or corrupt sectors are migrated within the database to new locations. However, the sectors do not physically exist on disk. Instead, the reference to the sector should be removed.
Version
No response
What operating system are you running (e.g. Ubuntu 22.04, macOS, Windows 11)?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: