From: Eric Wong <email@example.com>
Subject: Re: [PATCH] dtas-archive: paranoid archival script
Date: Fri, 18 Sep 2015 08:54:01 +0000 [thread overview]
Message-ID: <20150918085401.GA8610@dcvr.yhbt.net> (raw)
Eric Wong <firstname.lastname@example.org> wrote:
> +dtas-archive is intended for archiving audio data to/from laptops and
> +computers without ECC memory, attempting to read data multiple times in
> +an attempt to detect memory corruption. dtas-archive may only be
> +effective on machines running the Linux kernel where posix_fadvise(2)
> +can be used to drop caches for a particular file after fsync(2).
> +dtas-archive spawns sox(1) to archive audio data (likely uncompressed
> +WAVE) to FLAC and verifies the result using sndfile-cmp(1), a tool
> +implemented by different than sox and less likely to share the same bugs
> +(if any) as sox.
Fwiw, I'm VERY happy to note this script actually just detected an error
the kernel + ECC RAM did not notice. The sox wav-to-flac copy was
corrupted, and sndfile-cmp caught the error after dropping the cache and
re-comparing. I tried remounting the device just in case, but running
sndfile-cmp by hand reproduced the error.
Again, this was from my workstation with ECC memory, even, so the error
probably happened on the USB or device level. I was just copying a WAV
file recording from a MicroSD card off a USB card reader.
Fwiw, I've been doing this cache-dropping + sndfile-cmp dance for nearly
3 years, now (with a different, unpublished script) now and this is my
first time detecting a real error.
I haven't listened, but stats off the corrupt copy did indicate
So the paranoia with verifying copies really is justified :>
prev parent reply other threads:[~2015-09-18 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 7:47 [PATCH] dtas-archive: paranoid archival script Eric Wong
2015-09-18 8:54 ` Eric Wong [this message]
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://80x24.org/dtas/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).