From owner-freebsd-proliant@FreeBSD.ORG Sat May 3 21:46:58 2008 Return-Path: Delivered-To: freebsd-proliant@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 136CE1065674 for ; Sat, 3 May 2008 21:46:58 +0000 (UTC) (envelope-from ulf@alameda.net) Received: from mail.alameda.net (mail.alameda.net [194.55.105.10]) by mx1.freebsd.org (Postfix) with ESMTP id D50F58FC3C for ; Sat, 3 May 2008 21:46:57 +0000 (UTC) (envelope-from ulf@alameda.net) Received: by mail.alameda.net (Postfix, from userid 1000) id 61D3333C25; Sat, 3 May 2008 14:46:50 -0700 (PDT) Date: Sat, 3 May 2008 14:46:50 -0700 From: Ulf Zimmermann To: Todorov Message-ID: <20080503214649.GW26105@evil.alameda.net> References: <480FC4FB.5020709@paladin.bulgarpress.com> <4818FFB8.90900@paladin.bulgarpress.com> <481AA213.1090103@delphij.net> <481AC6E1.6070109@ultra-secure.de> <20080502170130.GU26105@evil.alameda.net> <20080503142435.GA2923@exuma.irbs.com> <20080503173623.GV26105@evil.alameda.net> <481CD51A.3050906@paladin.bulgarpress.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <481CD51A.3050906@paladin.bulgarpress.com> User-Agent: Mutt/1.4.2.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 5.3-STABLE X-ANI-MailScanner-Information: Please contact the ISP for more information X-ANI-MailScanner: Found to be clean X-ANI-MailScanner-From: ulf@alameda.net Cc: ulf@Alameda.net, freebsd-proliant@freebsd.org Subject: Re: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 X-BeenThere: freebsd-proliant@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ulf@Alameda.net List-Id: "Technical discussion of FreeBSD on HP ProLiant server platforms." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2008 21:46:58 -0000 On Sun, May 04, 2008 at 12:11:54AM +0300, Todorov wrote: > |>> Backup, yes do it. But here is how to do it: > |>> > |>> hpacucli ctrl slot=0 ld 1 add drives=allunassigned > |>> > |>> This should add the additional drives to your first logical drive and > |>> expand it. Whenever I do this, I reboot now so FreeBSD sees the > |>> new larger physical disk. > |>> > |>> In most cases now you have to update the partition table, either > |>> by addition another slice or changing the size of your FreeBSD slice. > |>> > |>> If the file system you want to grow is the last one in disklabel, you > |>> can use disklabel to change the size of it, also the total line (c:) > |>> needs to grow. > |>> > |>> And then finally you can use growfs on the file system. > |> Growfs on 6.X will destroy your UFS2, and mabye UFS1, filesystem. > |> The patch in bin/115174 appeared to fix growfs but I recently had > |> a file system related panic on a machine with a growfs expanded > |> filesystem. > |> > |> reboot after panic: ffs_alloccg: map corrupted > |> > |> That panic may be unrelated to growfs but that machine is the only > |> 6.3 machine I have in production with a grown file system. The > |> 800G fileystem had a few percent used when it paniced. It was being > |> brought into service as a Cyrus IMAP replica. > |> > |> A working growfs was a requirement for me to move from rock solid > |> 4.11. It would really be nice if the filesystem guru's could take > |> a look at the growfs problem. > |> > |> John Capo > |> Tuffmail.com > | I just recently did a growfs in the describe method on: > | > | log01 ulf /home/ulf > uname -a > | FreeBSD log01.autc.com 6.1-STABLE FreeBSD 6.1-STABLE #0: Tue Jul 18 > | 06:32:28 PDT 2006 root@:/usr/obj/usr/src/sys/LOG i386 > | > | That machine had a pair of 72GB drives, I swapped one drive at a time to > | 300GB. Then ran "hpacucli ctrl sl=0 ld=1 modify size=max", rebooted into > | linux (small partition on the server) to use the fdisk there, rebooted > | back into FreeBSD, it saw the larger drive, larger partition. Then I > | edited "disklabel -e /dev/da0s4" to edit slice c: and f:. Ran growfs, > fsck. > | and voila I had more space for my logs. > | > > I've checked today and what was before - 2 disks in Logical RAID 1+0 > drive. By default they were mirrored as they are not 4. Today I've added > two more (4 total) and make EXPAND to the logical drive. This process > finished but the BIOS tool and the FBSD see the size of one disk, not > two as it should be. > > 4x146GB in RAID 1+0, FBSD see 136GB as /dev/da0 (shown in the message > during boot). Also the BIOS says logical drive is 136G and is ok. > > Should do EXTEND of the logical drive also - is this an option? hpacucli ctrl sl=0 array A show hpacucli ctrl sl=0 ld 1 show That will show the current status. If you are going to just create a new partition/file system anyways, you don't have to extent, you could just create a new logical disk, it would show as da1. To do that: hpacucli ctrl sl=0 array A create type=ld raid=1 That will use whatever space is available in array A (if the current status is that the two new drives have been added to array A). Of in case the drives are still seperate you can create an array B. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://www.Alameda.net/~ulf/resume.html