From owner-freebsd-stable Mon May 27 12:46:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98]) by hub.freebsd.org (Postfix) with ESMTP id 2FF8337B40B for ; Mon, 27 May 2002 12:46:10 -0700 (PDT) Received: from myhakas.estpak.ee (myhakas.estpak.ee [194.126.115.54]) by MX1.estpak.ee (Postfix) with ESMTP id 81E80887F4; Mon, 27 May 2002 22:45:54 +0300 (EEST) Received: from myhakas.estpak.ee (localhost [127.0.0.1]) by myhakas.estpak.ee (8.12.3/8.12.3) with ESMTP id g4RJk8HS014708; Mon, 27 May 2002 22:46:08 +0300 (EEST) (envelope-from vallo@myhakas.estpak.ee) Received: (from vallo@localhost) by myhakas.estpak.ee (8.12.3/8.12.3/Submit) id g4RJk7Ad014707; Mon, 27 May 2002 22:46:07 +0300 (EEST) Date: Mon, 27 May 2002 22:46:07 +0300 From: Vallo Kallaste To: David J Duchscher Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020527194607.GA14628@myhakas.estpak.ee> Reply-To: kalts@estpak.ee References: <20020527084348.GA9774@myhakas.estpak.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 27, 2002 at 02:19:42PM -0500, David J Duchscher wrote: > >Have you had dying disk in your vinum R5 configuration? If yes can > >you please tell me how you rebuilt new disk? I have had no luck > >rebuilding failed disk while filesystem on the degraded array is > >mounted and user I/O going on. The disk will be rebuilt and > >filesystem will be corrupted. I'm able to reproduce it at will with > >either SCSI or ATA disks, no matter on what system I try it. > > Have you tried these instructions: > > http://www.vinumvm.org/vinum/replacing-drive.html Yes I'm aware of these, no I'm not in need of them because of failure simulation only. While testing (simulating) replace and rebuild of failed drive there's no need to physically remove nor repartition disk. You'll place load on filesystem residing on R5 array, then simply force stop (stop -f) one subdisk. After a while running in degraded mode will simply start the subdisk again and reviving process starts. At the end you can be sure that newfs and restore of data is in order. Haven't had any other experience. Smells like FUD but isn't. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message