Re: [opensuse] Strange file corruption problem
- From: Bob Williams <linux@xxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 10 Jan 2010 19:00:18 +0000
Thanks, Carlos
You have grasped the setup exactly ...
On Sunday 10 Jan 2010 15:12:30 Carlos E. R. wrote:
On Sunday, 2010-01-10 at 08:29 -0000, Bob Williams wrote:
I have two systems, let's call them 'home' and 'away'. When I buy a music
CD, I rip it onto whichever machine is available, and convert it to flac.
I keep copies on both machines by rsyncing, so each machine's music
collection is a mirror of the other. Both collections are on encrypted
partitions. So far, so good.
'Away' plays the music perfectly, whereas 'home' has some corrupted
tracks which have small skips and louder pops and crackles in the
playback. The errors are reproducible, in that they occur in the same
place each time. It makes no difference which end the original ripping
took place, whether at 'home' or 'away'.
let me see:
- 2 machines
- encripted storage ¿type?
luKs
- rip on any, copied to the other using rsyncCorrect
- some tracks bad on machine "home".
- bad file on "home" is bad on "away" if copied via scp
Correct?
I would try comparing a "bad" file with the same file on the otherTwo objections to that solution:
machine. My guess is that they willbe different, and thus, it would prove
that "rsync" botched the job, and worse, it does not detect it.
1) Files that were ripped on "home" get corrupted, presumably _after_ a good
copy has been rsynced to "away", though I can't prove that. Generally, the
synchronisation will take place within a few days of ripping. The mirroring
has been going on for 3 or 4 years.
2) Why would rsync only botch things in one direction. You'd expect to find
damaged files at both ends, surely. Although, come to think of it, there is
some asymmetry, in that rsync both pushes and pulls from "away", while "home"
runs an 'always on' rsync daemon.
I'll take a look at that.and:
smartctl --all /dev/sdj
Find out if you have remapped (reallocated) sectors. It is in the list of
attributes. If so, a sector could have been remapped while containing data
and would explain the problem.
Bob
--
Registered Linux User #463880 FSFE Member #1300
GPG-FP: A6C1 457C 6DBA B13E 5524 F703 D12A FB79 926B 994E
openSUSE 11.2, Kernel 2.6.31.8-0.1-desktop, KDE 4.3.4
Intel Core2 Quad Q9400 2.66GHz, 4GB DDR RAM, nVidia GeForce 9200GS
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Follow-Ups:
- Re: [opensuse] Strange file corruption problem
- From: Carlos E. R.
- Re: [opensuse] Strange file corruption problem
- From: Bob Williams
- Re: [opensuse] Strange file corruption problem
- References:
- [opensuse] Strange file corruption problem
- From: Bob Williams
- Re: [opensuse] Strange file corruption problem
- From: Carlos E. R.
- [opensuse] Strange file corruption problem
- Prev by Date: Re: [opensuse] Opensuse 11.2, KDE4 Factory:, yast
- Next by Date: Re: [opensuse] Strange file corruption problem
- Previous by thread: Re: [opensuse] Strange file corruption problem
- Next by thread: Re: [opensuse] Strange file corruption problem
- Index(es):
Relevant Pages
|