From owner-freebsd-questions Sat Oct 28 10: 3:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from malkav.snowmoon.com (ip-208-20-126-237.cdcsd.k12.ny.us [208.20.126.237]) by hub.freebsd.org (Postfix) with SMTP id 60A0F37B479 for ; Sat, 28 Oct 2000 10:03:51 -0700 (PDT) Received: (qmail 74262 invoked from network); 28 Oct 2000 17:03:50 -0000 Received: from localhost.snowmoon.com (HELO localhost) (127.0.0.1) by localhost.snowmoon.com with SMTP; 28 Oct 2000 17:03:50 -0000 Date: Sat, 28 Oct 2000 13:03:50 -0400 (EDT) From: Jaime To: Jesse Cc: freebsd-questions@freebsd.org Subject: Re: handling disk failures with vinum In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 28 Oct 2000, Jesse wrote: > So.. is vinum capable of continuing to operate when a drive fails, or will > the system always die block on accesses and require a reboot? > I'm hoping the system can continue to operate during a failure, even if > I'm not around to reboot the system. I'm running 4.1-STABLE. I don't recall what I did, but when I tested my RAID-5 vinum set up, it continued to function. When I did this, I don't think that I pulled the power cable while a write was occuring, though. Also, after plugging the offending drive back into its power supply, I had to login as root and use the vinum command line tool in order to make the array realize that its drive was back. Then it conducted the rebuilding of that drive. However, I was able to cat a text file and echo >> to that file while the drive was unplugged. Jaime To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message