Date: Sun, 25 Mar 2007 18:06:27 -0700 From: George Hartzell <hartzell@cyrusharmon.com> To: Joe Kelsey <joe@zircon.seattle.wa.us> Cc: freebsd-stable@freebsd.org, Ivan Voras <ivoras@fer.hr> Subject: Re: gmirror Issues Message-ID: <61BEDB50-42B8-4B6C-BD48-70B98E4EB0D5@cyrusharmon.com> In-Reply-To: <4607100B.5050807@zircon.seattle.wa.us> References: <4606E163.9000506@zircon.seattle.wa.us> <eu6qvc$ja7$1@sea.gmane.org> <4607100B.5050807@zircon.seattle.wa.us>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 25, 2007, at 5:12 PM, Joe Kelsey wrote:
> Ivan Voras wrote:
>> Joe Kelsey wrote:
>>
>>
>>> So, after loading the mirror stuff, I regularly lock up the
>>> system by
>>> trying to perform simple activities on the mirror. What do I
>>> need to do
>>> differently?
>>>
>>> Here are the relevant dmesg lines:
>>> atapci0: <SiI 3512 SATA150 controller> port
>>> 0xa000-0xa007,0x9800-0x9803,0x9400-0x9407,0x9000-0x9003,0x8800-0x880
>>> f
>>> mem 0xfba00000-0xfba001ff irq 18 at device 13.0 on pci0
>>>
>>
>> I did almost the same thing you did with gmirror on 6.2-release on
>> amd64
>> the other day and it worked. There were several complaints about
>> "SiI"
>> hardware in the past, though - you might want to search the lists.
>>
>>
> Thank you for the suggestion, but it does not help. There is some
> traffic on the list about the 3112, but I have a 3512, which does
> not have any list traffic about bugs.
>
> The major thing that needs doing is a detailed explanation of how
> to take two brand new disk drives and mirror them. Nothing in the
> documentation discusses this. Do you have to create file systems
> on the drives first? Do you have to use fdisk to slice them up?
> Is there a size limit on drives? I am trying to mirror two 400G
> drives, is this supported? There is no information anywhere that I
> can find about these topics.
Have you seen this:
http://people.freebsd.org/~rse/mirror/
g.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61BEDB50-42B8-4B6C-BD48-70B98E4EB0D5>