Avoid data Corruption


6 posts in this topic Last Reply

Recommended Posts

ok,

Let's assume my server has 3 HDD + 1 parity HDD.

In case of a silent corruption (or bit rot) on a single file, a new parity will be computed.

And now way to detect or prevent the file corruption, neither restore it to its healthy state.

Because there ar no checksum verification.

Link to post

There is a hashdeep package available via unMenu. It's mostly useful for drives with static content, e.g., archive or full media drives. It takes about 8 hours to create hashes for a 2T drive. A shell script should be able to limit it to only processing only new or updated files which should be much faster.

Link to post

Again I would ask, where are you experiencing this? I've read plenty of ZFS arguments about this but I remain pretty unconvinced that it's as common as asserted. My movies play, my compressed files aren't corrupted, and people with encrypted file systems aren't having them drop like flies. All of these things would be occurring if this issue was so common. HDD have a great deal of error correction built in, overcoming this is isn't trivial.

 

Create hashes for your files to detect it, create PAR files to correct for it, but I don't think you'll find yourself utilizing them and a great deal of effort maintaining them....

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.