From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <4672ddba9b22be0ab00effce6cae068f@quanstro.net> References: <140e7ec30909121108l411080bam3a34bac1168f911f@mail.gmail.com> <4672ddba9b22be0ab00effce6cae068f@quanstro.net> Date: Tue, 15 Sep 2009 02:43:37 +0800 Message-ID: <140e7ec30909141143t5c700ed3ka9ad3437ce9dfee1@mail.gmail.com> From: sqweek To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] sd(3) and concurrent readers/writers? Topicbox-Message-UUID: 6eaa7516-ead5-11e9-9d60-3106f5b1d025 2009/9/13 erik quanstrom : >=C2=A0but i was > wondering why cmp would just work. =C2=A0it occurred to me that > i could run the dds in parallel with a command like this > =C2=A0 =C2=A0 =C2=A0 =C2=A0cmp <{dd -if data -bs 64k -count 20000} <{dd -= if ../sda1/data -bs 64k -count 20000} Cmp was actually my original method, it wasn't until things started going funny that I switched to md5sum, to rule out <{} as a potential problem source and get some more feedback on the blocks themselves. > surprisingly, this was just as fast on my setup as the specalized > program That is interesting to hear though :) -sqweek PS. not much progress on my server - having trouble getting ethernet up to connect to sources and check out your sd stuff.