Bit rot, a myth?

Currently reading
Bit rot, a myth?

963
322
NAS
DS620slim, DS415+
Operating system
  1. Linux
  2. macOS
  3. Windows
Mobile operating system
  1. Android
  2. iOS
My view on the bit rot topic is that it is a "popular" word for degradation issues we are all aware off.
It is used mainly by the marketing departments by soft and hardware manufacturers to scare us and sell us additional tools and additional hardware.

My point: things get old, for sure things like electromagnetic storage degrades, as part of regular wear/tear and also if not used, over time.
No news and nothing to worry if you just use your common sense and replace stuff as you used to do.
 
I took 70 TB of data (about 300,000 files) and stored two copies on separate sets of hard drives. One set went into cold storage, the other set was used actively and moved/copied around between different drives and filesystems. The set in cold storage was spun up once a year to keep the bearing fluid from settling. The active set was moved/copied around in its entirety maybe 5 times in total (say, 350 TB of transfers). All RAM was non-ECC. Drives were consumer models across a mix of all brands. The active set spent one year in ZFS under FreeBSD (when I was feeling particularly paranoid about bitrot and wanted file CRCs), the rest of the time in NTFS under Windows 7.

After 7 years, I ran an MD5 check on both sets of data.
Read on...
 
Last edited:
Exact my point, just electromagnetic degradation on 7 year old, partly cold stored unused disks. 12 files on 300.000 0.004%. Nothing to worry about, certainly not if you have double backups or change your disks before they reach EOL.
No panic, nothing new.

I would like to add (set in perspective) that a risk for full (100%) data loss in a 3 disk RAID 5 in 10 years time is around 0.005%, which means a full data loss risk is way higher than those few in the quoted "bit rot" issue.

 
Last edited by a moderator:
I tend to agree. I have yet to knowingly encounter true 'bit rot' in any of my computing activities, and being a fairly old fart I have data archives going back to 1990 at least. Then again, I've not gone explicitly looking for it either.
I use ZFS for my main storage nowadays, but this is primarily for its ease of use / centralisation of LVM / fs / RAID layers rather than its checksumming.

I understand why you'd want this level of security if you are a financial institution or landing spacecraft on the moon with the data - the cost of 'just in case' protection is worth it vs the disastrous consequences of an even very low chance of bit-flips - but I think it is an issue that has gained currency via internet forums more than from real life incidents.

Corporations do all sorts of stuff in the name of compliance, which aren't necessarily reflected in real life situations.
 
I just had a bunch checksum error on my synology raid with 4.5year old (crap) iron wolf drives. Not a myth.
How do you know it was a bit flip? The fact that it was 'a bunch' suggests something else, like a dodgy cable or that one of your 'crap' drives was dying. By their nature, bitflips have to be single, and random.

Drives die all the time. We're talking specifically about 'bitflips', ie when a cosmic ray or similar causes a single, random bit to change its value without any prosaic hardware / dead disk stuff being the cause.
 
How do you know it was a bit flip? The fact that it was 'a bunch' suggests something else, like a dodgy cable or that one of your 'crap' drives was dying. By their nature, bitflips have to be single, and random.

Drives die all the time. We're talking specifically about 'bitflips' here, ie when a cosmic ray or similar causes a single, random bit to change its value without any hardware / dead disk stuff being the cause.

Bit rot refers to things other than a bit flip IMO. Particularly the "rot" part, of decay, which likely is from a drive starting to go, or a weak part of the drive, over the years succumbing.

Bit flips, are bit flips. Neutrinos hitting ram, ARE, a thing, and now happen with a frequency of once a day or more, if you have enough ram.


I'm not sure how neutrinos interplay with hard drives. I guess it could flip a bit there too, but never studied the topic.
 
Bit rot refers to things other than a bit flip IMO. Particularly the "rot" part, of decay, which likely is from a drive starting to go, or a weak part of the drive, over the years succumbing.
Ok you have redefined 'bit rot' to mean any sort of failure, mechanical or otherwise, of a drive.
That's your prerogative, but it then becomes a discussion without meaning because, afaia, nobody is disputing that drives can fail, over time, for mechanical reasons.
Believe me, myself and the posters above had a more specific definition of 'bit rot' in mind when they posted :)
 
Ok you have redefined 'bit rot' to mean any sort of failure, mechanical or otherwise, of a drive.
That's your prerogative, but it then becomes a discussion without meaning because, afaia, nobody is disputing that drives can fail, over time, for mechanical reasons.
Believe me, myself and the posters above had a more specific definition of 'bit rot' in mind when they posted :)

Yea, because you know the "true" meaning and one else can. Because the "rot" part of a brand new drive being hit by a neutrino sounds so apropos of 'bitROT'. And it's not any type, because I'm saying specifically not a bit flip.

If youre using the term incorrectly, don't be surprised if discussions get off track:

 
I dont think a dictionary is going to solve our communications impasse...I'll repectifully bow out of this one and leave the floor to you, sir.

Wishing you a great NYE! (y):)
 
Nice discussion!
The issue is that every error, even checksum errors are now called bitrot, while it can be caused by many hard disk failures. The term is useless in my world...
 
When I ran Windows Home Server I used to run a couple of utilites to validate the integrity of the data. One was intelligent re-write. I would keep track of sectors that have data and if they weren't accessed over a period of time it would do random reads against them and also a re-write and checksum analysis. And it never detected any "rot" but did lead to discovering bad sectors on two WD drives.

Many of these utilites dont get to see the real ECC rate of the data as stored since the drives proprietary firmware manages the physical layer of the drive.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

I must say, in this day and age of law suits everywhere, they’re really brave to have a product like this!
Replies
2
Views
2,001
Replies
14
Views
4,297

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top