From owner-freebsd-current Thu May 23 18:11: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from november.debolaz.com (november.debolaz.com [193.71.19.191]) by hub.freebsd.org (Postfix) with ESMTP id E93AB37B40B for ; Thu, 23 May 2002 18:11:00 -0700 (PDT) Received: from amphibic.com (november [193.71.19.191]) by november.debolaz.com (Postfix) with SMTP id 215B113603B; Fri, 24 May 2002 03:10:59 +0200 (CEST) Received: from 62.179.190.82 (SquirrelMail authenticated user debolaz) by webmail.debolaz.com with HTTP; Fri, 24 May 2002 03:10:59 +0200 (CEST) Message-ID: <49879.62.179.190.82.1022202659.squirrel@webmail.debolaz.com> Date: Fri, 24 May 2002 03:10:59 +0200 (CEST) Subject: Re: Vinum problem From: "Anders Nor Berle" To: In-Reply-To: References: X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I have no possibility to get new large disk now. > Should I try to remove plex usr.p1 ? > Sounds like it's related to a problem I encountered with vinum some time ago. For me, vinum would bail out in panic if I tried to access an area of a volume that was not initialized on the mirrored plex. This was only a problem before the mirrored plex was fully initialized the first time though (which tends to be a slow process on big disks). So basically, if the plex had no mapped physical counterpart, it would under certain situations cause a panic if you attempted to use these areas on the plex. (I know it's area based, because when I tried to newfs the volume, the panic occured proportional to the initialization percentage) If this is the reason, it's not a lot of other things to do than get a disk big enough to hold the complete plex, or remove the plex (I haven't tried if removing the plex works, so that's just a guess). - Anders Nor Berle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message