Date: Wed, 2 Aug 2006 18:32:55 -0500 From: "Rick C. Petty" <rick-freebsd@kiwi-computer.com> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-geom@freebsd.org Subject: Re: gmirror Cannot add disk ad5 to gm0 (error=22) Message-ID: <20060802233255.GB16385@megan.kiwi-computer.com> In-Reply-To: <44D12A80.9040802@quip.cz> References: <44D06650.1030803@quip.cz> <20060802183001.GA14279@megan.kiwi-computer.com> <44D10D1D.9040700@quip.cz> <20060802210709.GA15310@megan.kiwi-computer.com> <44D126EF.9070503@quip.cz> <44D12A80.9040802@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 03, 2006 at 12:43:12AM +0200, Miroslav Lachman wrote: > > Something is definitely wrong. Gmirror status still shows 0% after > couple of minutes (normaly synchronization progress is about 1% per minute) Under what conditions do you define "normally"? I think you can tweak the numbers to make it go faster or slower, and I think it's dependent upon (disk) idle time. > systat -vmstat shows less then 1MB/s instead of usual 40MB/s, but 100% busy. > > Disks ad4 ad5 > KB/t 121 128 > tps 4 4 > MB/s 0.45 0.45 > % busy 83 103 What other activity is happening on the box? Are you in the middle of a background fsck? What does the output of "atacontrol mode ad4" (and ad5) show? Are you sure your "normal" synchronization happened when you were in IDE mode instead of AHCI? > Is there any chance to found source of problems without step by step > replacement of each component? That depends upon the problems. To diagnose anything, you need to be able to reliably bring down the mirror-- e.g. heavy disk activity. > I can't believe that I have bad cables in > 4 new machines or bad hard drives in each machine... :o( I bought identical machines (cpus, boards, disks, cables, etc.) and had different results on each. Especially when you buy identical stuff, there is a small probability that they'll all have the same problems-- for example, a bad batch of disks. In your case, I'd investigate which steps you have to preform to repeatably cause the failures. On my systems, the heavier the disk load, the higher the probability of failure. Upgrading to the latest 6.1-STABLE might help in some cases. -- Rick C. Petty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060802233255.GB16385>