| Blogs | Classifieds | Downloads | FlashChat | Gallery | Googlemap | Invite Friends | Links | Projects | Reviews | Wiki |
| |||||||||
Welcome to the pSeries Tech Forums,
our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software. You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments. Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community. Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
| Our Sponsors | |
| | |
| Want to advertise? | |
![]() |
| | LinkBack | Thread Tools |
|
#1
| ||||
| ||||
I have a setup with 2 VIO Servers and 3 AIX5L logical partitions. I needed to increase the amount of physical partitions available for rootvg on the three AIX partitions. I added some additional hard drives to my system and attempted to increase my clients datavg and rootvg LV's. On the VIO Servers I added the new PV's to the clientlpar_vg. I then increased the size of the logical volumes that present themselves as hdisk on the AIX client partitions (two Lvols one for rootvg and one for datavg on the client Lpars). On each of the AIX client Lpars I first did a chvg -g on the datavg volume group to make the additional space available on the client. Then I was able to do chfs and increase the size of my data lvols. I tried the same process with the rootvg volume group and chvg -g failed. I later found some documentation that said the only to increase the rootvg on a client lpar is to create another lvol on the VIO servers that presents as another PV on the client partition, and then add this new PV to the clients rootvg volume group. So now that I know how I should have increased the rootvg's on my client lpars, I can't. I cannot do it because all the space (physical disk partitions ) was allocated to the VIO's Lvols (which present as PVs for rootvg on the client). Even though I was never able to make the space allocation available on the client using chvg -g It was allocated to the VIO's lvol. Is there a way to re-aquire the space allocated to the VIO's lvol without destroying my clients rootvg and everything on it. |
|
#2
| ||||
| ||||
Are the rootvgs mirrored?
__________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. Fred Sherman IBM pSeries and Storage Architect |
|
#4
| ||||
| ||||
Unmirror rootvg Remove hdisk1 from rootvg rmdev -l hdisk1 -d cfgmgr Verify hdisk1 now has the new size Add hdisk1 to rootvg Mirror rootvg sync AND WAIT TO COMPLETE Redo for hdisk0
__________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. Fred Sherman IBM pSeries and Storage Architect |
|
#5
| ||||
| ||||
attempted to follow procedure given. used smit to unmirror and re-mirror volume group also did syncvg -v rootvg from command prompt . Now lpar won't boot and goes to the Power PC firmware screen Firmware screen seems to recognize that there should be to disk to boot from; but does not see them as bootable. Not sure where what went wrong, I tried to follow procedure as given. Any additional help will be appreciated |
|
#6
| ||||
| ||||
When you mirror/unmirror rootvg, the OS always instructs you to reset the bootlist and run bosboot -a. Did you do that?
__________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. Fred Sherman IBM pSeries and Storage Architect |
|
#8
| ||||
| ||||
ARe you able to direct SMS to boot from one of the disks?
__________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. Fred Sherman IBM pSeries and Storage Architect |
|
#10
| ||||
| ||||
Here's what you're going to have to do. Create another small LV for that LPAR and BOS install it. When the LPAR boots up on that hdisk, do an import for the other disks: importvg altinst_rootvg hdiskx The volume group name IS important. Set your bootlist for the hdisks of altinst_rootvg and run bosboot -a Those drives should now be bootable. Reboot into SMS and specify those drives.
__________________ To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. Fred Sherman IBM pSeries and Storage Architect |
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| NIM server and client operations | steevojb | Tutorials | 22 | 1 Week Ago 01:35 |
| Microsoft Windows 2003 Active Directory integration | FASherman | Tutorials | 25 | April 28th, 2008 07:14 |
| Vio Client san disk allocation | datamax | IBM PowerVM Editions | 2 | February 21st, 2007 03:43 |
| Lost SAN connection/0514-038 Error loading kernel extension | paulmann | pSeries - System p | 3 | December 14th, 2006 18:54 |