From owner-freebsd-current@FreeBSD.ORG Thu Apr 26 14:26:12 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A4FF716A407 for ; Thu, 26 Apr 2007 14:26:12 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 75BBB13C44B for ; Thu, 26 Apr 2007 14:26:12 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l3QEQ2fB065412; Thu, 26 Apr 2007 09:26:02 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4630B67A.90604@freebsd.org> Date: Thu, 26 Apr 2007 09:26:02 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Ivan Voras References: <33910a2c0704260533l5afcb1actacd3bf1980b46cfc@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88.4/3165/Thu Apr 26 08:03:24 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-current@freebsd.org Subject: Re: GVirstor Label problem on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Apr 2007 14:26:12 -0000 On 04/26/07 08:36, Ivan Voras wrote: > Jason Hills wrote: >> I know it is plenty new code. But I am getting a problem: >> >> ./gvirstor label -v -s 2097152 myvol ad8s1d >> Total virtual chunks: 524288 (4 MB each), 2097152 MB total virtual size. >> >> Clearing metadata on ad3s1d. >> Writing allocation table to ad3s1d... (4 MB, 1 chunks) >> Tried to write 4194304, written 4294967295 (Operation not permitted) >> Error writing out allocation map! >> >> ad8s1d is unmounted; I tried newfs´ing it but the problem remains; > > A possible reason could be that the virstor map is larger than your > physical storage (I think I don't have a check for this in the code > [yet]). How large is ad3s1d? > > I'll notify you and the list when I modify the code. > Maybe he has another partition/slice used and GEOM debugflags needs to be set? Eric