Skip to content
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

Source read errors - assume zeros #20

Open
Evengard opened this issue Apr 10, 2022 · 0 comments
Open

Source read errors - assume zeros #20

Evengard opened this issue Apr 10, 2022 · 0 comments

Comments

@Evengard
Copy link

Sometimes when copying a block device, you stumble upon bad sectors. It could happen with any drive, and it could be as small as 1 sector on the whole drive.
Unfortunately, diskrsync just stops on read error.
Sometimes backing up whatever you can from that drive to a remote location is the only option - because you don't have enough space to run ddrescue locally.
Sure, I don't ask to implement ddrescue inside diskrsync. But it would be nice that on a read error, diskrsync just assumed the read returned all zeroes and kept transfering other data.
This mode may be non-default and be enabled with some kind of flag. Still, this would allow to preserve the rest of the data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant