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

Reproducible data corruption, not detected, not corrected. #359

Open
onlyjob opened this issue Dec 22, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@onlyjob
Copy link
Contributor

commented Dec 22, 2014

I've configured both OSDs to verify default Adler32 checksums:

checksums.algorithm = Adler32
checksums.enabled = true

OSDs were restarted and the above settings were confirmed on the DIR server web page.

A bunch of files with known SHA1 digests were written with --replication-policy WaR1 --replication-factor 2 but there is a catch: I've deliberately used HDD with faulty firmware on one OSD to check how well XtreemFS handles corruption in data (i.e. bitrot). Verification of some files failed without raising any errors on client side. No errors appeared in OSD log either.

FYI LizardFS passed similar test where XtreemFS and Ceph are failed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.