Reid Linnemann wrote:
> Written by Wojciech Puchar on 06/03/09 15:58>>
> > i simply have in crontab a script running once per hour:
> >
> > #!/bin/sh
> > /sbin/gmirror status|grep -q DEGRADED && \\
> > mail -s "gmirror failure" myphonenum...@mygsmoperator.pl
> Surely you jest! You presume that I
or bad cables.
I'll have to try different cables sometime, you may very well be correct.
i had such problems many times. it always was cables or disk drive.
Disk drive - check with smartmontools from ports.
i simply have in crontab a script running once per hour:
#!/bin/sh
/sbin/gmirror s
Written by Wojciech Puchar on 06/03/09 15:58>>
>> My mirror gm0 consists of two SATA disks, ad4 and ad6. Now, I have a
>> finicky controller that sporadically spits out READ_DMA and READ_DMA48
>
> or bad cables.
>
I'll have to try different cables sometime, you may very well be correct.
>> time
My mirror gm0 consists of two SATA disks, ad4 and ad6. Now, I have a
finicky controller that sporadically spits out READ_DMA and READ_DMA48
or bad cables.
timeouts inexplicably. So at some point in time immemorial after
installing the last kernel, ad4 suffered a number of READ_DMA48 errors
and
I was recently updating my 7-STABLE system from a 7.1-PRERELEASE era
tree, and after having quite an unexpected headache doing so I have a
few words of wisdom.
When updating FreeBSD, treat it like a car and ALWAYS CHECK YOUR MIRRORS!
My mirror gm0 consists of two SATA disks, ad4 and ad6. Now, I h
