From owner-freebsd-isp  Wed Jun 20 21:16:47 2001
Delivered-To: freebsd-isp@freebsd.org
Received: from misery.sdf.com (misery.sdf.com [204.244.213.49])
	by hub.freebsd.org (Postfix) with ESMTP id AB61837B401
	for <freebsd-isp@freebsd.org>; Wed, 20 Jun 2001 21:16:43 -0700 (PDT)
	(envelope-from tom@sdf.com)
Received: from tom (helo=localhost)
	by misery.sdf.com with local-esmtp (Exim 2.12 #1)
	id 15Cvib-0004qz-00; Wed, 20 Jun 2001 21:05:21 -0700
Date: Wed, 20 Jun 2001 21:05:18 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Troy Settle <troy@psknet.com>
Cc: "Forrest W. Christian" <forrestc@imach.com>,
	freebsd-isp@FreeBSD.ORG
Subject: RE: RAID/vinum options (mail server)
In-Reply-To: <GIEHKBHPBGKJPNMBCOHFKECNCBAA.troy@psknet.com>
Message-ID: <Pine.BSF.4.05.10106202101450.19245-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-isp.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-isp>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-isp>
X-Loop: FreeBSD.org


On Wed, 20 Jun 2001, Troy Settle wrote:

> 
> Not so lucky :(
> 
> The degraded message didn't show up until after reboot (as part of the
> device ID when the kernel is reading the disk label.  The information is
> stored in DMESG.
> 
> The only RAID card that I know of with tools in the OS is Mylex (man
> mlxcontrol).  I can't tell from the man page if you can actually do anything
> useful (like detach a physical drive, reattach, start a rebuild, etc...).
> 
> I guess this is one area where NT has left us behind :(

  mlxcontrol can trigger rebuilds of arrays on the mlx driver, not the
mly.  It is pretty much automatic:  just hookup the new drive, and issue
the rebuild command.  Of course, I was using a managed enclosure, so
things like detaching the physical drive, and re-attach are automatic.

  Using the mly driver things actual seem easier.  Disk failures are
reported to syslog.  Removing the disk, and plugging in the new disk
triggers a rebuild which is also reported to syslog.  When the array is
back to full state, it is logged to syslog as well.  The only management
tool I need is something to check the health in case I miss a syslog
message.  Everything else is automatic.


Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message