On Mon, 07 Jan 2013 21:11:35 +0100 Florian Philipp <li...@binarywings.net> wrote:
> Hi list! > > I have a use case where I am seriously concerned about bit rot [1] > and I thought it might be a good idea to start looking for it in my > own private stuff, too. > > Solving the problem is easy enough: > - Record checksums and timestamps for each file > - Check and update records via cronjob > - If checksum changed but timestamp didn't, notify user > - Let user restore from backup > > However, I haven't found any application in portage for this task. > Now, the implementation is easy enough but I'm wondering why it > hasn't been done. Or do I just look for the wrong thing? The only > suitable thing seems to be app-admin/tripwire but that application > also looks like overkill. > > [1] http://en.wikipedia.org/wiki/Bit_rot > > Regards, > Florian Philipp > You are using a very peculiar definition of bitrot. "bits" do not "rot", they are not apples in a barrel. Bitrot usually refers to code that goes unmaintained and no longer works in the system it was installed. What definition are you using? If you mean crummy code that goes unmaintained, then keep systems up to date and report bugs. If you mean disk file corruption, then doing it file by file is a colossal waste of time IMNSHO. You likely have >1,000,000 files. Are you really going to md5sum each one daily? Really? This is a filesystem task, not a cronjab task. Use a filesystem that does proper checksumming. ZFS does it, but that is of course somewhat problematic on Linux. Check out the others, it will be something modern you need, like ext4 maybe or btrfs -- Alan McKinnon alan.mckin...@gmail.com
