From owner-freebsd-geom@FreeBSD.ORG Tue Aug 1 20:43:18 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 802FA16A4DD for ; Tue, 1 Aug 2006 20:43:18 +0000 (UTC) (envelope-from nomad@castle.org) Received: from castle.org (castle.org [207.178.4.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0215643D46 for ; Tue, 1 Aug 2006 20:43:17 +0000 (GMT) (envelope-from nomad@castle.org) Received: from [128.208.232.198] (vanyel.ee.washington.edu [128.208.232.198]) (authenticated bits=0) by castle.org (8.13.6/8.13.6) with ESMTP id k71KhE55031897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Aug 2006 13:43:15 -0700 (PDT) (envelope-from nomad@castle.org) Message-ID: <44CFBCDE.7040003@castle.org> Date: Tue, 01 Aug 2006 13:43:10 -0700 From: Lee Damon User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719) MIME-Version: 1.0 To: Eric Anderson References: <44CFB4AB.4080803@castle.org> <44CFB908.40904@centtech.com> In-Reply-To: <44CFB908.40904@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on castle.org Cc: freebsd-geom@freebsd.org Subject: Re: growfs, old disks, gvinum - filesystem expansion and corruption X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Aug 2006 20:43:18 -0000 > = Eric Anderson >> = me ... >> My questions are: >> 1. Is there any way to clean up the old file system cruft without >> crashing/trashing/deleting the system? > > You could use dd to write zeros over the old areas to wipe out the old > filesystem data. Careful! Is there a way to find out which parts of the "disk" are currently not in use by an active gvinum area? >> 2. What tool should I be using to calve off slices of a 'huge' drive >> and later expand it? > > Why not use fdisk/bsdlabel? I didn't think that could be done with a live/active/mounted drive or with more than a handful of slices. [The system currently has 16 mounted gvinum-based filesystems, some of which will end up being made of 3 (or more) individual slices based on growth]. nomad