From owner-freebsd-questions@FreeBSD.ORG Sun Jun 27 08:54:19 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D839F16A4CE for ; Sun, 27 Jun 2004 08:54:19 +0000 (GMT) Received: from mail.digitalpath.net (ns1.digitalpath.net [65.164.104.5]) by mx1.FreeBSD.org (Postfix) with SMTP id 3989843D31 for ; Sun, 27 Jun 2004 08:54:19 +0000 (GMT) (envelope-from rholmes@digitalpath.net) Received: (qmail 17592 invoked by uid 1546); 27 Jun 2004 08:54:18 -0000 Received: from rholmes@digitalpath.net by pop by uid 504 with qmail-scanner-1.22 (clamscan: 0.65. Clear:RC:1(12.25.190.12):. Processed in 0.160371 secs); 27 Jun 2004 08:54:18 -0000 Received: from 12-25-190-12.roseville.ca.digitalpath.net (HELO guppy) (12.25.190.12) by ns1.digitalpath.net with SMTP; 27 Jun 2004 08:54:18 -0000 Message-ID: <000301c45c24$b5a3de90$0a00a8c0@guppy> From: "Richard Holmes" To: Date: Sun, 27 Jun 2004 01:57:00 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: terabyte limit problem with vinum X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jun 2004 08:54:20 -0000 Shawn, Did you ever find a solution to the terabyte limit problem you reported last year on FreeBSD.Questions (09/06/2003 and 01/12/2004). I'm having exactly the same problem. I've got eight Maxtor 250GB SATA drives ganged together into one big RAID5 volume with a net size of 1636GB. Everything is fine until "newfs -U -O2 /dev/vinum/..." gives the "can't read old UFS1 superblock" error. I'm using FreeBSD 5.2.1 csvup'd to REL_ENG_5_2 in mid June 2004. Thanks, Richard Holmes Lambda Software Development Rocklin, CA (916) 390-2057 (cell) rholmes@midtown.net rholmes@digitalpath.net (soon to be discontinued) P.S. I've also been having some other problems with vinum. "vinum resetconfig" doesn't always wipe out all of the vinum drives and seems to not reliably erase the vinum database from all of the drives. After resetconfig, "vinum list" may show one or two drives remaining. To get rid of them all, I need to do multiple cycles of "vinum rm -f -r", "vinum stop" and "vinum start". Have also had problems with empty vinum volumes being corrupted after reboot (remember "newfs" failed, so nothing was ever written to the volume). After successfully creating and initializing the vinum RAID5 volume, I "stop" it, then reboot. After reboot, vinum insists on reinitializing the entire volume (an 8 hour process).