On Mon, 19 Feb 2007, Anton Yuzhaninov wrote:
AY> DM> 1. Name: ad4g
AY> DM>Mediasize: 225734096384 (210G)
AY> DM>Sectorsize: 512
AY> DM>Mode: r1w1e1
AY> DM>State: ACTIVE
AY> DM>Priority: 0
AY> DM>Flags: BROKEN
AY>
AY> Is any related messages about ad4g in /var/log/messages?
On Mon, 19 Feb 2007, Oliver Fromme wrote:
OF> Dmitry Morozovsky <[EMAIL PROTECTED]> wrote:
OF> > [EMAIL PROTECTED]:/usr/local/etc# gmirror status m0g
OF> > NameStatus Components
OF> > mirror/m0g DEGRADED ad4g
OF> > ad6g (100%)
OF>
OF> It seems that the secon
Dmitry Morozovsky <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED]:/usr/local/etc# gmirror status m0g
> NameStatus Components
> mirror/m0g DEGRADED ad4g
> ad6g (100%)
It seems that the second disk is broken and locks up the
channel near the end of the disk.
Yo
Hello Dmitry,
You wrote on Sunday, February 18, 2007, 9:53:14 PM:
DM> 1. Name: ad4g
DM>Mediasize: 225734096384 (210G)
DM>Sectorsize: 512
DM>Mode: r1w1e1
DM>State: ACTIVE
DM>Priority: 0
DM>Flags: BROKEN
Is any related messages about ad4g in /var/log/messages?
--
Anton Y
Dear colleagues,
today I've found that one of two disks had been removed from a couple of
gmirror'ed partiotions dur to read timeout. I have done `gmirror forget' and
`gmirror insert', and it works for relatively small partitions; however, on
rather large partiotion it did sync, and then stalls
