From delphij at delphij.net Fri May 2 05:09:53 2008 From: delphij at delphij.net (Xin LI) Date: Fri May 2 05:09:57 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <4818FFB8.90900@paladin.bulgarpress.com> References: <480FC4FB.5020709@paladin.bulgarpress.com> <4818FFB8.90900@paladin.bulgarpress.com> Message-ID: <481AA213.1090103@delphij.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Todorov wrote: | Hi all, | | I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 | bacause I have two disks inserted in RAID 1+0 Logical drive), add two | more disks and get actual RAID 1+0 drive of four disks. | | I was reading the ACU specs of HP and I see this can be done online. I | can have downtime - the question is if I can do it w/o dump and restore | of the filesystem? | | I fully realize that the size will be doubled of /dev/da0 device, | currently 136GB will become 272GB. Can I make a spare partition of it, | will the whole procedure happen w/o any dump/restore? I think you should at least take a backup before resizing anything regardless if there is any mechanism that allows you to do it without a full restore. With regards to the resizing, for UFS there is a program called 'growfs' but I think there are few users who used it, so potentially it could use more time if you decided to use it :( Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgaohIACgkQi+vbBBjt66C59gCeLpXiiSBDsWAHVFYnDuTIlJL0 qcgAoLHecEJYpS0W6VkXLwwteDG58UjB =FKXm -----END PGP SIGNATURE----- From rainer at ultra-secure.de Fri May 2 07:46:47 2008 From: rainer at ultra-secure.de (Rainer Duffner) Date: Fri May 2 07:46:53 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <481AA213.1090103@delphij.net> References: <480FC4FB.5020709@paladin.bulgarpress.com> <4818FFB8.90900@paladin.bulgarpress.com> <481AA213.1090103@delphij.net> Message-ID: <481AC6E1.6070109@ultra-secure.de> Xin LI schrieb: > Todorov wrote: > | Hi all, > | > | I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 > | bacause I have two disks inserted in RAID 1+0 Logical drive), add two > | more disks and get actual RAID 1+0 drive of four disks. > | > | I was reading the ACU specs of HP and I see this can be done online. I > | can have downtime - the question is if I can do it w/o dump and restore > | of the filesystem? > | > | I fully realize that the size will be doubled of /dev/da0 device, > | currently 136GB will become 272GB. Can I make a spare partition of it, > | will the whole procedure happen w/o any dump/restore? > > I think you should at least take a backup before resizing anything That, and I think you will end up with a 2nd DOS-partition that comprises the "added" free space. Regards, Rainer From notification at abbey.co.uk Fri May 2 10:56:25 2008 From: notification at abbey.co.uk (Abbey National) Date: Fri May 2 10:56:29 2008 Subject: Your account has been updated Message-ID: Account Update Notification Dear Customer, You have successfully changed your phone number online. In order to confirm or cancel the changes you have made, please click on t [1]Click here ** This is an automated message, please do not respond ** 2008 Abbey. All Rights Reserved. References 1. 3D"http://chronicpain4life.com/" From ulf at Alameda.net Fri May 2 17:01:37 2008 From: ulf at Alameda.net (Ulf Zimmermann) Date: Fri May 2 17:01:40 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <481AC6E1.6070109@ultra-secure.de> References: <480FC4FB.5020709@paladin.bulgarpress.com> <4818FFB8.90900@paladin.bulgarpress.com> <481AA213.1090103@delphij.net> <481AC6E1.6070109@ultra-secure.de> Message-ID: <20080502170130.GU26105@evil.alameda.net> On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: > Xin LI schrieb: > >Todorov wrote: > >| Hi all, > >| > >| I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 > >| bacause I have two disks inserted in RAID 1+0 Logical drive), add two > >| more disks and get actual RAID 1+0 drive of four disks. > >| > >| I was reading the ACU specs of HP and I see this can be done online. I > >| can have downtime - the question is if I can do it w/o dump and restore > >| of the filesystem? > >| > >| I fully realize that the size will be doubled of /dev/da0 device, > >| currently 136GB will become 272GB. Can I make a spare partition of it, > >| will the whole procedure happen w/o any dump/restore? > > > >I think you should at least take a backup before resizing anything > > > That, and I think you will end up with a 2nd DOS-partition that > comprises the "added" free space. 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. -- 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 From jc at irbs.com Sat May 3 14:36:13 2008 From: jc at irbs.com (John Capo) Date: Sat May 3 14:36:17 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080502170130.GU26105@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> Message-ID: <20080503142435.GA2923@exuma.irbs.com> Quoting Ulf Zimmermann (ulf@Alameda.net): > On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: > > Xin LI schrieb: > > >Todorov wrote: > > >| Hi all, > > >| > > >| I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 > > >| bacause I have two disks inserted in RAID 1+0 Logical drive), add two > > >| more disks and get actual RAID 1+0 drive of four disks. > > >| > > >| I was reading the ACU specs of HP and I see this can be done online. I > > >| can have downtime - the question is if I can do it w/o dump and restore > > >| of the filesystem? > > >| > > >| I fully realize that the size will be doubled of /dev/da0 device, > > >| currently 136GB will become 272GB. Can I make a spare partition of it, > > >| will the whole procedure happen w/o any dump/restore? > > > > > >I think you should at least take a backup before resizing anything > > > > > > That, and I think you will end up with a 2nd DOS-partition that > > comprises the "added" free space. > > 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 > > -- > 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 > _______________________________________________ > freebsd-proliant@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-proliant > To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" From todorov at paladin.bulgarpress.com Sat May 3 15:12:19 2008 From: todorov at paladin.bulgarpress.com (Todorov) Date: Sat May 3 15:12:24 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080503142435.GA2923@exuma.irbs.com> 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> Message-ID: <481C80C3.3000606@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Capo ??????: | Quoting Ulf Zimmermann (ulf@Alameda.net): |> On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: |>> Xin LI schrieb: |>>> Todorov wrote: |>>> | Hi all, |>>> | |>>> | I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 |>>> | bacause I have two disks inserted in RAID 1+0 Logical drive), add two |>>> | more disks and get actual RAID 1+0 drive of four disks. |>>> | |>>> | I was reading the ACU specs of HP and I see this can be done online. I |>>> | can have downtime - the question is if I can do it w/o dump and restore |>>> | of the filesystem? |>>> | |>>> | I fully realize that the size will be doubled of /dev/da0 device, |>>> | currently 136GB will become 272GB. Can I make a spare partition of it, |>>> | will the whole procedure happen w/o any dump/restore? |>>> |>>> I think you should at least take a backup before resizing anything |>> |>> That, and I think you will end up with a 2nd DOS-partition that |>> comprises the "added" free space. |> 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 | | | | |> -- |> 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 |> _______________________________________________ |> freebsd-proliant@freebsd.org mailing list |> http://lists.freebsd.org/mailman/listinfo/freebsd-proliant |> To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" | _______________________________________________ | freebsd-proliant@freebsd.org mailing list | http://lists.freebsd.org/mailman/listinfo/freebsd-proliant | To unsubscribe, send any mail to "freebsd-proliant-unsubscribe@freebsd.org" For now I will skip the growfs. If the controller migrate the level w/o any data lost will be great - I will do additional partition afterwards. I will send update. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgcgMMACgkQibJkIG65HMdj3ACdGAX6fOww6UAvWp6sDdCGG3P4 oa0AoIDkcpzVvqNDBe60ODXKjH/32aWR =D/Et -----END PGP SIGNATURE----- From ulf at Alameda.net Sat May 3 17:36:30 2008 From: ulf at Alameda.net (Ulf Zimmermann) Date: Sat May 3 17:36:33 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080503142435.GA2923@exuma.irbs.com> 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> Message-ID: <20080503173623.GV26105@evil.alameda.net> On Sat, May 03, 2008 at 10:24:35AM -0400, John Capo wrote: > Quoting Ulf Zimmermann (ulf@Alameda.net): > > On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: > > > Xin LI schrieb: > > > >Todorov wrote: > > > >| Hi all, > > > >| > > > >| I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 > > > >| bacause I have two disks inserted in RAID 1+0 Logical drive), add two > > > >| more disks and get actual RAID 1+0 drive of four disks. > > > >| > > > >| I was reading the ACU specs of HP and I see this can be done online. I > > > >| can have downtime - the question is if I can do it w/o dump and restore > > > >| of the filesystem? > > > >| > > > >| I fully realize that the size will be doubled of /dev/da0 device, > > > >| currently 136GB will become 272GB. Can I make a spare partition of it, > > > >| will the whole procedure happen w/o any dump/restore? > > > > > > > >I think you should at least take a backup before resizing anything > > > > > > > > > That, and I think you will end up with a 2nd DOS-partition that > > > comprises the "added" free space. > > > > 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. -- 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 From todorov at paladin.bulgarpress.com Sat May 3 21:12:09 2008 From: todorov at paladin.bulgarpress.com (Todorov) Date: Sat May 3 21:12:12 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080503173623.GV26105@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> Message-ID: <481CD51A.3050906@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ulf Zimmermann ??????: | On Sat, May 03, 2008 at 10:24:35AM -0400, John Capo wrote: |> Quoting Ulf Zimmermann (ulf@Alameda.net): |>> On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: |>>> Xin LI schrieb: |>>>> Todorov wrote: |>>>> | Hi all, |>>>> | |>>>> | I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 |>>>> | bacause I have two disks inserted in RAID 1+0 Logical drive), add two |>>>> | more disks and get actual RAID 1+0 drive of four disks. |>>>> | |>>>> | I was reading the ACU specs of HP and I see this can be done online. I |>>>> | can have downtime - the question is if I can do it w/o dump and restore |>>>> | of the filesystem? |>>>> | |>>>> | I fully realize that the size will be doubled of /dev/da0 device, |>>>> | currently 136GB will become 272GB. Can I make a spare partition of it, |>>>> | will the whole procedure happen w/o any dump/restore? |>>>> |>>>> I think you should at least take a backup before resizing anything |>>> |>>> That, and I think you will end up with a 2nd DOS-partition that |>>> comprises the "added" free space. |>> 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? Regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgc1RoACgkQibJkIG65HMcxnACcDu21hJWMqbRxVyD3FuI3Emb4 gBsAoM5l7CGG7fARqo7lJW5R6WM2Vs9I =w+Ev -----END PGP SIGNATURE----- From jc at irbs.com Sat May 3 21:24:58 2008 From: jc at irbs.com (John Capo) Date: Sat May 3 21:25:03 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080503173623.GV26105@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> Message-ID: <20080503212457.GA10705@exuma.irbs.com> Quoting Ulf Zimmermann (ulf@Alameda.net): > On Sat, May 03, 2008 at 10:24:35AM -0400, John Capo wrote: > > Quoting Ulf Zimmermann (ulf@Alameda.net): > > > On Fri, May 02, 2008 at 09:46:41AM +0200, Rainer Duffner wrote: > > > > Xin LI schrieb: > > > > >Todorov wrote: > > > > >| Hi all, > > > > >| > > > > >| I want to migrate my RAID1 (2 disks) (automatically assigned as RAID1 > > > > >| bacause I have two disks inserted in RAID 1+0 Logical drive), add two > > > > >| more disks and get actual RAID 1+0 drive of four disks. > > > > >| > > > > >| I was reading the ACU specs of HP and I see this can be done online. I > > > > >| can have downtime - the question is if I can do it w/o dump and restore > > > > >| of the filesystem? > > > > >| > > > > >| I fully realize that the size will be doubled of /dev/da0 device, > > > > >| currently 136GB will become 272GB. Can I make a spare partition of it, > > > > >| will the whole procedure happen w/o any dump/restore? > > > > > > > > > >I think you should at least take a backup before resizing anything > > > > > > > > > > > > That, and I think you will end up with a 2nd DOS-partition that > > > > comprises the "added" free space. > > > > > > 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. > My results are quite different. FreeBSD playground.irbs.net 6.3-RELEASE FreeBSD 6.3-RELEASE #19: Sat Mar 1 13:31:34 EST 2008 root@t232.irbs.com:/usr/local/bsd/src/sys/i386/compile/HP-SMP-6.2-PAE i386 This is a DL380 G3 with a 6402 controller. playground.irbs.net 1# fsck /dev/da6a ** /dev/da6a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 25867 files, 334539 used, 16614859 free (30091 frags, 2073096 blocks, 0.2% fragmentation) playground.irbs.net 2# disklabel -e da6 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 70000000 16 4.2BSD 2048 16384 28552 c: 143363040 0 unused 0 0 # "raw" part, don't edit 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 140000000 16 4.2BSD 2048 16384 28552 c: 143363040 0 unused 0 0 # "raw" part, don't edit playground.irbs.net 3# playground.irbs.net 3# growfs /dev/da6a We strongly recommend you to make a backup before growing the Filesystem Did you backup your data (Yes/No) ? Yes new file systemsize is: 35000000 frags Warning: 373408 sector(s) cannot be allocated. growfs: 68177.0MB (139626592 sectors) block size 16384, fragment size 2048 using 371 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 70001632, 70377984, 70754336, 71130688, 71507040, 71883392, 72259744, 72636096, 73012448, 73388800, 73765152, 74141504, 74517856, 74894208, 75270560, 75646912, 76023264, 76399616, 76775968, 77152320, 77528672, 77905024, 78281376, 78657728, 79034080, 79410432, 79786784, 80163136, 80539488, 80915840, 81292192, 81668544, 82044896, 82421248, 82797600, 83173952, 83550304, 83926656, 84303008, 84679360, 85055712, 85432064, 85808416, 86184768, 86561120, 86937472, 87313824, 87690176, 88066528, 88442880, 88819232, 89195584, 89571936, 89948288, 90324640, 90700992, 91077344, 91453696, 91830048, 92206400, 92582752, 92959104, 93335456, 93711808, 94088160, 94464512, 94840864, 95217216, 95593568, 95969920, 96346272, 96722624, 97098976, 97475328, 97851680, 98228032, 98604384, 98980736, 99357088, 99733440, 100109792, 100486144, 100862496, 101238848, 101615200, 101991552, 102367904, 102744256, 103120608, 103496960, 103873312, 104249664, 104626016, 105002368, 105378720, 105755072, 106131424, 106507776, 106884128, 107260480, 107636832, 108013184, 108389536, 108765888, 109142240, 109518592, 109894944, 110271296, 110647648, 111024000, 111400352, 111776704, 112153056, 112529408, 112905760, 113282112, 113658464, 114034816, 114411168, 114787520, 115163872, 115540224, 115916576, 116292928, 116669280, 117045632, 117421984, 117798336, 118174688, 118551040, 118927392, 119303744, 119680096, 120056448, 120432800, 120809152, 121185504, 121561856, 121938208, 122314560, 122690912, 123067264, 123443616, 123819968, 124196320, 124572672, 124949024, 125325376, 125701728, 126078080, 126454432, 126830784, 127207136, 127583488, 127959840, 128336192, 128712544, 129088896, 129465248, 129841600, 130217952, 130594304, 130970656, 131347008, 131723360, 132099712, 132476064, 132852416, 133228768, 133605120, 133981472, 134357824, 134734176, 135110528, 135486880, 135863232, 136239584, 136615936, 136992288, 137368640, 137744992, 138121344, 138497696, 138874048, 139250400 playground.irbs.net 4# playground.irbs.net 4# fsck /dev/da6a ** /dev/da6a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes PARTIALLY ALLOCATED INODE I=4383968 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4383972 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4384032 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4384033 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4384034 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4384035 CLEAR? [yn] y PARTIALLY ALLOCATED INODE I=4384036 CLEAR? [yn] ^C playground.irbs.net #5 I have not the the balls to mount and use a grown file system without doing an fsck first. I'll try that and see what happens. John Capo From ulf at Alameda.net Sat May 3 21:46:58 2008 From: ulf at Alameda.net (Ulf Zimmermann) Date: Sat May 3 21:47:03 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <481CD51A.3050906@paladin.bulgarpress.com> 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> Message-ID: <20080503214649.GW26105@evil.alameda.net> 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 From todorov at paladin.bulgarpress.com Sat May 3 22:11:09 2008 From: todorov at paladin.bulgarpress.com (Todorov) Date: Sat May 3 22:11:14 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <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> <20080503214649.GW26105@evil.alameda.net> Message-ID: <481CE2F9.3050109@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ulf Zimmermann ??????: | 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. | Let me ask since I got confused... 4 disks in RAID 1+0 (let's assume I don't want to extend the FS) should be seen as two RAID 1 's ? Should I see the RAID 0 somewhere also? Can you please provide some output of the dmesg or camcontrol inquiry . Many thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgc4vkACgkQibJkIG65HMfBAQCePQ6a26hoirkNumvGN9skQBxX 6vkAnRT8g1zewWLC0HeBOiWqG7eeOlCz =iUot -----END PGP SIGNATURE----- From ulf at Alameda.net Sun May 4 05:47:34 2008 From: ulf at Alameda.net (Ulf Zimmermann) Date: Sun May 4 05:47:40 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <481CE2F9.3050109@paladin.bulgarpress.com> 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> <20080503214649.GW26105@evil.alameda.net> <481CE2F9.3050109@paladin.bulgarpress.com> Message-ID: <20080504054727.GX26105@evil.alameda.net> On Sun, May 04, 2008 at 01:11:05AM +0300, Todorov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ulf Zimmermann ??????: > | 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. > | > > Let me ask since I got confused... > > 4 disks in RAID 1+0 (let's assume I don't want to extend the FS) should > be seen as two RAID 1 's ? > > Should I see the RAID 0 somewhere also? > > Can you please provide some output of the dmesg or camcontrol inquiry . What does "hpacucli ctrl sl=0 array A show" show? -- 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 From todorov at paladin.bulgarpress.com Sun May 4 21:08:14 2008 From: todorov at paladin.bulgarpress.com (Todorov) Date: Sun May 4 21:08:18 2008 Subject: HP DL385G1 Smart Array 6i AMD64 FBSD 6.3 In-Reply-To: <20080504054727.GX26105@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> <20080503214649.GW26105@evil.alameda.net> <481CE2F9.3050109@paladin.bulgarpress.com> <20080504054727.GX26105@evil.alameda.net> Message-ID: <481E25AF.5090203@paladin.bulgarpress.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ulf Zimmermann ??????: | On Sun, May 04, 2008 at 01:11:05AM +0300, Todorov wrote: |> -----BEGIN PGP SIGNED MESSAGE----- |> Hash: SHA1 |> |> Ulf Zimmermann ??????: |> | 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. |> | |> |> Let me ask since I got confused... |> |> 4 disks in RAID 1+0 (let's assume I don't want to extend the FS) should |> be seen as two RAID 1 's ? |> |> Should I see the RAID 0 somewhere also? |> |> Can you please provide some output of the dmesg or camcontrol inquiry . | | What does "hpacucli ctrl sl=0 array A show" show? | It worked :) I couldn't use hpacucli under 6.3 AMD64 FreeBSD (if anyone could please let me know, as it didn't recognize the controller). So I used the SmartStart CD. I did expansion of the current RAID 1+0 (RAID1 actually as there were only 2 disks) with another 2 disks. So the expansion finished in about 6 hours and I saw OK for the volume BUT the size was the same as the RAID1 - - 146GB (4x146GB disks inside the logical drive). So I started asking myself if the process did something so I went onsite next day and started the ACU again - there was an option to EXTEND the SIZE as there was another 146GB free space unassigned to the previous size. I did this (few seconds) and the size became 280GB (MAX). Currently I have 280GB - there was a problem with the fdisk - it was warning me for the slices not starting on the beginning of the track which led to non bootable system (data was there but the boot loader told me - wrong part info). So I did it again and then override the boot loader - this time it was ok. In the FBSD I see /dev/da0 as RAID 1 which is strange but nevermind. Thanks Ulf for encouraging me to test this! I had backup for the other scenario but I did it w/o reinstall of the OS which was nice. There were some messages in syslog: May 4 15:42:13 opteron kernel: ciss0: *** Parity/consistency initialization complete, logical drive 0 May 4 15:42:13 opteron kernel: ciss0: logical drive 0 () completed consistency initialisation which I had to monitor for anycase if they are regular or just something with the last restart. Regards, Todorov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgeJa8ACgkQibJkIG65HMeiDwCg9w/DS6IZgyiFByPLxhXyGVG1 in4AoMh2zVUHHMqZNMJrMf0ds3zGVLKq =lB3C -----END PGP SIGNATURE----- From kama at pvp.se Mon May 19 13:10:35 2008 From: kama at pvp.se (kama) Date: Mon May 19 13:10:38 2008 Subject: DL380G5 boot problems. Message-ID: <20080519142817.T90572@ns1.as.pvp.se> Hi, I just got a DL380G5 that needs to run FreeBSD 6.0. (GENERIC kernel) The problem seems to be that the "HP Virual Keyboard" is stealing the keyboard and when I attach a USB keyboard it finds the keyboard but is "dead". If the keyboard is inserted at power on, it will works as expected. If I both have a USB and ps2 keyboard connected and remove the USB keyboard, the ps2 keyboard starts working. I have tried to disable the USB in the BIOS and use a ps2 keyboard, but with no luck. I have tried to find a way to disable the USB support in FreeBSD. Anyone had similar problems and know a way around this? Since these servers will later be located in a datacenter, I cant have a usb keyboard connected to each server all of the time. /Bjorn From hali at datapipe.net Mon May 19 14:51:01 2008 From: hali at datapipe.net (Hussain Ali) Date: Mon May 19 14:51:04 2008 Subject: dl320G5p Message-ID: <20080519144049.GI8203@datapipe.com> Hello, Just got some of these in. FreeBSD 6.3 paniced with the following "panic: interrupt missing from bus." Specs: - Quad-Core Intel? Xeon? processor 3210 - HP E200 (cciss) storage controller - Embedded NC326i Dual Port Gigabit Server Adapter (bge) Attached is a FreeBSD 7.0 64 bit dmesg and smbios information. -- -hussain This message may contain confidential or privileged information. If you are not the intended recipient, please advise us immediately and delete this message. See http://www.datapipe.com/emaildisclaimer.aspx for further information on confidentiality and the risks of non-secure electronic communication. If you cannot access these links, please notify us by reply message and we will send the contents to you. -------------- next part -------------- Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU X3210 @ 2.13GHz (2128.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20000800 AMD Features2=0x1 Cores per package: 4 usable memory = 2133049344 (2034 MB) avail memory = 2058391552 (1963 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Feb 24 2008 10:34:18) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 824082406000824 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 824082406000824 device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 824082406000824 device_attach: est2 attach returned 6 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 824082406000824 device_attach: est3 attach returned 6 p4tcc3: on cpu3 pcib0: on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci21: on pcib1 pcib2: at device 0.0 on pci21 pci24: on pcib2 pcib3: at device 4.0 on pci24 pci25: on pcib3 ciss0: port 0x4000-0x40ff mem 0xfdf80000-0xfdffffff,0xfdf70000-0xfdf77fff irq 16 at device 8.0 on pci24 ciss0: [ITHREAD] pcib4: at device 6.0 on pci0 pci18: on pcib4 pcib5: at device 28.0 on pci0 pci2: on pcib5 pcib6: at device 0.0 on pci2 pci3: on pcib6 bge0: mem 0xfdef0000-0xfdefffff,0xfdee0000-0xfdeeffff irq 16 at device 4.0 on pci3 miibus0: on bge0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge0: Ethernet address: 00:1f:29:bd:e6:c4 bge0: [ITHREAD] bge1: mem 0xfded0000-0xfdedffff,0xfdec0000-0xfdecffff irq 17 at device 4.1 on pci3 miibus1: on bge1 brgphy1: PHY 1 on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bge1: Ethernet address: 00:1f:29:bd:e6:c5 bge1: [ITHREAD] pcib7: at device 28.2 on pci0 pci4: on pcib7 pcib8: at device 28.3 on pci0 pci7: on pcib8 pcib9: at device 28.4 on pci0 pci10: on pcib9 pcib10: at device 28.5 on pci0 pci13: on pcib10 uhci0: port 0x1000-0x101f irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1020-0x103f irq 21 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1040-0x105f irq 21 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1060-0x107f irq 21 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfdbf0000-0xfdbf03ff irq 21 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: waiting for BIOS to give up control usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib11: at device 30.0 on pci0 pci1: on pcib11 vgapci0: port 0x3000-0x30ff mem 0xd8000000-0xdfffffff,0xfddf0000-0xfddfffff irq 21 at device 2.0 on pci1 pci1: at device 4.0 (no driver attached) pci1: at device 4.2 (no driver attached) uhci4: port 0x3800-0x381f irq 23 at device 4.4 on pci1 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: <(0x103c) UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb5 uhub5: 2 ports with 2 removable, self powered pci1: at device 4.6 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1080-0x1087,0x1088-0x108b,0x1090-0x1097,0x1098-0x109b,0x10a0-0x10af,0x10b0-0x10bf irq 20 at device 31.2 on pci0 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] atapci1: port 0x10c0-0x10c7,0x10c8-0x10cb,0x10d0-0x10d7,0x10d8-0x10db,0x10e0-0x10ef,0x10f0-0x10ff irq 20 at device 31.5 on pci0 atapci1: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse Explorer, device ID 4 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] orm0: at iomem 0xc0000-0xcafff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: [FILTER] vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: on uhub5 kbd2 at ukbd0 ums0: on uhub5 ums0: X report 0x0002 not supported device_attach: ums0 attach returned 6 uhub6: on uhub5 uhub6: 7 ports with 7 removable, self powered Timecounters tick every 1.000 msec hptrr: no controller detected. da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 135.168MB/s transfers da0: 34699MB (71065440 512 byte sectors: 255H 32S/T 8709C) acd0: DVDROM at ata4-master UDMA33 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Trying to mount root from ufs:/dev/da0s1a ukbd1: on uhub3 kbd3 at ukbd1 uhid0: on uhub3 ums0: on uhub3 ums0: 3 buttons and Z dir. ums0: at uhub3 port 2 (addr 3) disconnected ums0: detached ukbd1: at uhub3 port 1 (addr 2) disconnected ukbd1: detached uhid0: at uhub3 port 1 (addr 2) disconnected uhid0: detached bge0: link state changed to DOWN bge0: link state changed to UP smbios.bios.reldate="02/26/2008" smbios.bios.vendor="HP" smbios.bios.version="W05" smbios.chassis.maker="HP" smbios.chassis.serial="MX2814001E " smbios.chassis.tag=" " smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="HP" smbios.system.product="ProLiant DL320 G5p" smbios.system.serial="MX2814001E " smbios.system.uuid="34343534-3335-4d58-3238-313430303145"