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
Now instead of barfing fs internals at the user and having them figure out what that do with that information and re-start the replace job from the beginning (until the next unrecoverable error is found), it would be much better if the filesystem could automatically remove those unrecoverable files and continue with the device replace.
The text was updated successfully, but these errors were encountered:
When a
btrfs replace
is unable the recover a file on a raid56 array, it will just abort:There is a formula to translate those magic numbers back to a file, for convenience I moved that to a shell script:
(assuming 4k sectors and 64k stripes)
Now instead of barfing fs internals at the user and having them figure out what that do with that information and re-start the replace job from the beginning (until the next unrecoverable error is found), it would be much better if the filesystem could automatically remove those unrecoverable files and continue with the device replace.
The text was updated successfully, but these errors were encountered: