From owner-freebsd-questions@FreeBSD.ORG Sun Feb 20 07:40:14 2005 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 3254116A4CE for ; Sun, 20 Feb 2005 07:40:14 +0000 (GMT) Received: from stewie.obfuscated.net (stewie.obfuscated.net [66.118.188.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AB1643D3F for ; Sun, 20 Feb 2005 07:40:13 +0000 (GMT) (envelope-from m@obmail.net) Received: from [192.168.1.100] (653259hfc120.tampabay.res.rr.com [65.32.59.120]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by stewie.obfuscated.net (Postfix) with ESMTP id 15C3460D1 for ; Sun, 20 Feb 2005 02:40:13 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: FreeBSD Mailing List From: Michael Conlen Date: Sun, 20 Feb 2005 02:40:11 -0500 X-Mailer: Apple Mail (2.619.2) Subject: growfs 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, 20 Feb 2005 07:40:14 -0000 On FreeBSD 5.3 I added disks to a disk array. The array contained two 250 GB disks stripped (actually four mirrored and striped but it's all done in hardware). I added two more pairs to the virtual disk, rebooted the machine, rewrote the disklabel for the additional capacity and ran growfs. It would grow the filesystem to almost the end and reported growfs: rdfs: seek error: : unknown error: 0 I ran growfs with progressively smaller -s options, but the same thing happens when it gets near the end of the new size of the file system. fdisk reports the new size for the disk in sectors on partition 1 and the cylinders, heads and sectors/track appear proper. the only odd thing I notice is that nfs2# fdisk -s /dev/da1s1 /dev/da1s1: 121341 cyl 255 hd 63 sec Part Start Size Type Flags 4: 0 50000 0xa5 0x80 nfs2# fdisk -s /dev/da1 /dev/da1: 121342 cyl 255 hd 63 sec Part Start Size Type Flags 1: 63 1949359167 0xa5 0x80 notice da1s1 lists part 4 as size 50000 (25 MB). da1 lists the propersize. disklabel looks right for da1s1 nfs2# disklabel -r /dev/da1s1 # /dev/da1s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 1949359167 0 unused 0 0 # "raw" part, don't edit d: 1949359167 0 4.2BSD 2048 16384 28552 Now, I had gone through this process when upgrading from one pair to two without a problem. I'm not sure where to start looking for issues and am looking for a pointer of where to start looking or a better idea of what info I need to debug this. Does anyone see something completely out of whack?