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) Message-ID: <Pine.BSF.4.05.10106202101450.19245-100000@misery.sdf.com> In-Reply-To: <GIEHKBHPBGKJPNMBCOHFKECNCBAA.troy@psknet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.10106202101450.19245-100000>