From owner-freebsd-questions@FreeBSD.ORG Fri May 29 14:12:50 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D28A1065707 for ; Fri, 29 May 2009 14:12:50 +0000 (UTC) (envelope-from Vikash.Badal@is.co.za) Received: from phobytor.is.co.za (phobytor.is.co.za [196.4.160.171]) by mx1.freebsd.org (Postfix) with ESMTP id D682E8FC15 for ; Fri, 29 May 2009 14:12:49 +0000 (UTC) (envelope-from Vikash.Badal@is.co.za) Received: from phobytor.is.co.za (localhost [127.0.0.1]) by phobytor.is.co.za (Postfix) with ESMTP id D545A3BB975 for ; Fri, 29 May 2009 15:51:25 +0200 (SAST) Received: from ZABRYSVISMFW (zajnbisit.mfw.is.co.za [196.26.2.106]) by phobytor.is.co.za (Postfix) with ESMTP id A16FC3BB569 for ; Fri, 29 May 2009 15:51:25 +0200 (SAST) Received: from zabrysvisex06.af.didata.local (Not Verified[10.1.8.16]) by ZABRYSVISMFW with MailMarshal (v6, 1, 8, 2172) id ; Fri, 29 May 2009 15:51:28 +0200 Received: from ZABRYSVISEX04.af.didata.local ([10.1.8.149]) by zabrysvisex06.af.didata.local with Microsoft SMTPSVC(6.0.3790.3959); Fri, 29 May 2009 15:51:25 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 x-cr-hashedpuzzle: Zl8= Ad+9 BTrJ BzM2 B/M5 Cefe DAyb DXoI FsAa FtB9 GIZk Hcpx IN/H IcM/ Ic2S I2jZ; 1; ZgByAGUAZQBiAHMAZAAtAHEAdQBlAHMAdABpAG8AbgBzAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {D6DB3D8D-FE69-4EC2-8447-455F3812A3FD}; dgBpAGsAYQBzAGgALgBiAGEAZABhAGwAQABpAHMALgBjAG8ALgB6AGEA; Fri, 29 May 2009 13:51:15 GMT; ZwByAG8AdwBpAG4AZwAgAGEAIABnAHIAYQBpAGQAMwAgAGEAcgByAGEAeQAgAGEAbgBkACAAZwByAG8AdwBmAHMAIABuAG8AdAAgAGcAcgBvAHcAaQBuAGcAIAAuAC4ALgAuAA== MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable x-cr-puzzleid: {D6DB3D8D-FE69-4EC2-8447-455F3812A3FD} Content-class: urn:content-classes:message Date: Fri, 29 May 2009 15:51:15 +0200 Message-ID: <740109F1ED7BA14EB02307DEF26487AB1B554BB6@ZABRYSVISEX04.af.didata.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: growing a graid3 array and growfs not growing .... Thread-Index: AcngZIibzHd4/A+vRtq8AU9fU0t0wA== From: "Vikash Badal" To: X-OriginalArrivalTime: 29 May 2009 13:51:25.0487 (UTC) FILETIME=[8EDB7BF0:01C9E064] X-Virus-Scanned: ClamAV using ClamSMTP Subject: growing a graid3 array and growfs not growing .... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2009 14:12:51 -0000 Can someone please advise why growfs would return: growfs: we are not growing (8388607->4194303) ? I have a FreeBSD 7.2 server in a VM. I initially had 5 x 4G disks Created a raid graid3 label datavol da2 da3 da4 da5 da6 I upgraded them to 5 x 8g disks swopped out the virtual disks one at a time graid3 remove -n 0 datavol graid3 insert -n 0 datavol da2 [wait] ...... graid3 remove -n 4 datavol graid3 insert -n 4 datavol da6 [wait] graid3 stop datavol growfs /dev/raid3/datavol error message: growfs: we are not growing (8388607->4194303) ? vix-sw-raid# graid3 list Geom name: datavol State: COMPLETE Components: 5 Flags: NONE GenID: 0 SyncID: 1 ID: 2704170828 Zone64kFailed: 0 Zone64kRequested: 0 Zone16kFailed: 0 Zone16kRequested: 0 Zone4kFailed: 0 Zone4kRequested: 524 Providers: 1. Name: raid3/datavol =20 Mediasize: 34359736320 (32G) =20 Sectorsize: 2048 =20 Mode: r0w0e0 Consumers: 1. Name: da2 =20 Mediasize: 8589934592 (8.0G) =20 Sectorsize: 512 =20 Mode: r1w1e1 =20 State: ACTIVE =20 Flags: NONE =20 GenID: 0 =20 SyncID: 1 =20 Number: 0 =20 Type: DATA 2. Name: da3 =20 Mediasize: 8589934592 (8.0G) =20 Sectorsize: 512 =20 Mode: r1w1e1 =20 State: ACTIVE =20 Flags: NONE =20 GenID: 0 =20 SyncID: 1 =20 Number: 1 =20 Type: DATA 3. Name: da4 =20 Mediasize: 8589934592 (8.0G) =20 Sectorsize: 512 =20 Mode: r1w1e1 =20 State: ACTIVE =20 Flags: NONE =20 GenID: 0 =20 SyncID: 1 =20 Number: 2 =20 Type: DATA 4. Name: da5 =20 Mediasize: 8589934592 (8.0G) =20 Sectorsize: 512 =20 Mode: r1w1e1 =20 State: ACTIVE =20 Flags: NONE =20 GenID: 0 =20 SyncID: 1 =20 Number: 3 =20 Type: DATA 5. Name: da6 =20 Mediasize: 8589934592 (8.0G) =20 Sectorsize: 512 =20 Mode: r1w1e1 =20 State: ACTIVE =20 Flags: NONE =20 GenID: 0 =20 SyncID: 1 =20 Number: 4 =20 Type: PARITY fdisk /dev/raid3/datavol ******* Working on device /dev/raid3/datavol ******* parameters extracted from in-core disklabel are: cylinders=3D1044 heads=3D255 sectors/track=3D63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=3D1044 heads=3D255 sectors/track=3D63 (16065 blks/cyl) fdisk: invalid fdisk partition table found fdisk: /boot/mbr: length must be a multiple of sector size what am I missing ? Please note: This email and its content are subject to the disclaimer as = displayed at the following link http://www.is.co.za/legal/E-mail+Confiden= tiality+Notice+and+Disclaimer.htm. Should you not have Web access, send a= =20mail to disclaimers@is.co.za and a copy will be emailed to you.