From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id ACCD9138372 for ; Tue, 8 Jan 2013 17:38:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D26DD21C0DE; Tue, 8 Jan 2013 17:37:41 +0000 (UTC) Received: from mail-bk0-f48.google.com (mail-bk0-f48.google.com [209.85.214.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6974521C0D6 for ; Tue, 8 Jan 2013 17:35:41 +0000 (UTC) Received: by mail-bk0-f48.google.com with SMTP id jc3so414600bkc.35 for ; Tue, 08 Jan 2013 09:35:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding :content-type; bh=rbdbgi2dLv2CWAIm8IYsmU1iQrnmkPRzgyV1b+tbZk0=; b=fSaPIXiqqhmVIiCAKDS0aFkpEnFSdogy2fVLtpsSv1fXjVKMbMpFHBi3FdtUQfY2VX egvwDcTowkpxE0+PWToZRlSMer2zvPDA5i6VHqEUNoboAmvo5edbiXrOny+nN6o1sqku IXkuFPesrqvp7+w5gFpAVXJnttL+seIorRPz85S4WnMeS8lO70YEr8oHfpSOSgO9oQB6 6j0k9ENvQVhvnf94WvHQPDRyeLG1TumUkRzRysoGGg3bk7bThF1iXmsJZh93GxFsji3H 5J9Ukcffuk1eelEFjMMd+zy2fgo9umpzSJy5ME+8XaKg0OtHXc/SAc56RAymyN3p7k46 1PAQ== X-Received: by 10.204.147.25 with SMTP id j25mr31907536bkv.36.1357666539892; Tue, 08 Jan 2013 09:35:39 -0800 (PST) Received: from localhost.localnet (p4FC602C5.dip0.t-ipconnect.de. [79.198.2.197]) by mx.google.com with ESMTPS id c10sm46226573bkw.1.2013.01.08.09.35.38 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Jan 2013 09:35:39 -0800 (PST) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Cc: Florian Philipp Subject: Re: [gentoo-user] OT: Fighting bit rot Date: Tue, 08 Jan 2013 18:35:36 +0100 Message-ID: <3613897.q2tncFpUrH@localhost> User-Agent: KMail/4.9.5 (Linux/3.4.24; KDE/4.9.5; x86_64; ; ) In-Reply-To: <50EBCA77.8030603@binarywings.net> References: <50EB2BF7.4040109@binarywings.net> <20130108012016.2f02c68c@khamul.example.com> <50EBCA77.8030603@binarywings.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: b44f0f9c-1d29-44ac-93d0-f34063dd246a X-Archives-Hash: 4558cc1e20427456a7484da7277c1287 Am Dienstag, 8. Januar 2013, 08:27:51 schrieb Florian Philipp: > Am 08.01.2013 00:20, schrieb Alan McKinnon: > > On Mon, 07 Jan 2013 21:11:35 +0100 > > > > Florian Philipp 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. > > [...] > > >> [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? > > That's why I referred to wikipedia, not the jargon file ;-) > > The definition that I thought about was decay of storage media, > especially hard disks. I'm not aware of another commonly used name for > that effect. Disk rot seems to apply only to optical media. > > > 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? > > Well, not daily but often enough that I likely still have a valid copy > as a backup. and who guarantees that the backup is the correct file? btw, the solution is zfs and weekly scrub runs. -- #163933