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 D82B213835F for ; Tue, 8 Jan 2013 08:01:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8379321C071; Tue, 8 Jan 2013 08:01:06 +0000 (UTC) Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C308121C069 for ; Tue, 8 Jan 2013 07:59:33 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id x43so83314wey.37 for ; Mon, 07 Jan 2013 23:59:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=5CvpxWhxaluD4ghBDiXc6DUqOY80a9hdW3pjxJDm1CU=; b=SySOhpKzN+Npg+xk9WmCDtx+/FBTa2wR3ECv15AX87shjLOHT8qVXOtfosraAL8szh qTPQg7H04ob7ejmD7PlZ+xD7HNKg6H37EM73rHW0wXtCGtemEtCmg712uOQ9zP48u46+ BOVIJqaYta53danJMrMsas+Mq7KcvOSQGikN//awS6BhS+Q/kRwB6i5H1MiggXZwi5Re INXj1EGJW7U5L/3SAfYkIFCZj6FkmOq3IaJEoYXNNakxNZEpO/+7SltDHelJ3UkEZnR+ gnV08WO8rjJFn7fkwo1wPYFAnTpKL9F8Udlj2HqEPBEkUhHOhUjc05tdcDhUdWO3IHbc fb0Q== X-Received: by 10.194.108.101 with SMTP id hj5mr2254901wjb.6.1357631972423; Mon, 07 Jan 2013 23:59:32 -0800 (PST) Received: from khamul.example.com (196-215-209-117.dynamic.isadsl.co.za. [196.215.209.117]) by mx.google.com with ESMTPS id ex6sm17276944wid.3.2013.01.07.23.59.30 (version=SSLv3 cipher=OTHER); Mon, 07 Jan 2013 23:59:31 -0800 (PST) Date: Tue, 8 Jan 2013 09:55:10 +0200 From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] OT: Fighting bit rot Message-ID: <20130108095510.04f84040@khamul.example.com> In-Reply-To: <50EBCA77.8030603@binarywings.net> References: <50EB2BF7.4040109@binarywings.net> <20130108012016.2f02c68c@khamul.example.com> <50EBCA77.8030603@binarywings.net> Organization: Internet Solutions X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.14; x86_64-pc-linux-gnu) 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-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 8d8101d5-9e09-43da-8b77-1ccdb6b1fb12 X-Archives-Hash: 2fb5976dd687e7839ff2c3474bb094cc On Tue, 08 Jan 2013 08:27:51 +0100 Florian Philipp wrote: > > 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 > > > > AFAIK, ext4 only has checksums for its metadata. Even if the file > system would support appropriate checksums out-of-the-box, I'd still > need a tool to regularly read files and report on errors. > > As I said above, the point is that I need to detect the error as long > as I still have a valid backup. Professional archive solutions do > this on their own but I'm looking for something suitable for desktop > usage. rsync might be able to give you something close to what you want easily Use the -n switch for an rsync between your originals and the last backup copy, and mail the output to yourself. Parse it looking for ">" and "<" symbols and investigate why the file changed. This strikes me as being a very easy solution that you could use reliably with a suitable combination of options. -- Alan McKinnon alan.mckinnon@gmail.com