3 ms·
This comment has two parts - the first one I think deserves more attention. When your program can actively and randomly rot while it's in in production, the onl
by falcolas 11y ago
This comment has two parts - the first one I think deserves more attention. When your program can actively and randomly rot while it's in in production, the only valid recovery method really is "power cycling" the application. As the OS is also being affected by this rot, power cycling the OS is a valid solution to many problems as well.
The push for making broad use of consumer hardware running production environments to save (a veritable fistfull of) money has only made this problem worse.
It makes me wonder if we shouldn't be adding a module to the Linux kernel to occasionally reload blocks of code from disk.
- crististm 11y ago"occasionally reload blocks of code from disk" - It's not that simple. An ECC system avoids most HW related issues but does not protect you from SW errors which probably accounts for most rotting. Why reboot it in the first place? If the HW has ECC, the SW does not rot unless it is poorly written.