This is tested on AIX 6.1. When you try to add a disk to an existing VG, by doing:
#extendvg vgdata hdisk20
you may receive the following error message:
0516-1714 /usr/sbin/extendvg: The total number of partitions on the disks for this volume group would be 184302, which exceeds the current maxpps value of 131072. Increase the maxpps value to 262144 using the chvg -P command, then retry. 0516-792 /usr/sbin/extendvg: Unable to extend volume group"
The cause?
bash-3.00# lsvg vgdata VOLUME GROUP: vgdata VG IDENTIFIER: 00c39a0200004c000000012bb22891c2 VG STATE: active PP SIZE: 8 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 122871 (182952 megabytes) MAX LVs: 256 FREE PPs: 1 (8 megabytes) LVs: 2 USED PPs: 111870 (982960 megabytes) OPEN LVs: 2 QUORUM: 2 (Enabled) TOTAL PVs: 2 VG DESCRIPTORS: 3 STALE PVs: 0 STALE PPs: 0 ACTIVE PVs: 2 AUTO ON: yes MAX PPs per VG: 131072 MAX PVs: 1024 LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no HOT SPARE: no
As you can see, the current maxpps per vg for the vgdata volume group is 131072 pps, and to increase the size of the vg from 1TB to 1.5TB requires 184302. To solve this problem, we need to increase the value of the maxpps parameter for the vgdata volume group. Just follow the on screen clue to perform:
#chvg -P 262144 vgdata
Now, make sure that the maxpps value has been altered:
bash-3.00# lsvg dumpvg VOLUME GROUP: dumpvg VG IDENTIFIER: 00c39a0200004c000000012bb22891c2 VG STATE: active PP SIZE: 8 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 122871 (182952 megabytes) MAX LVs: 256 FREE PPs: 1 (8 megabytes) LVs: 2 USED PPs: 122870 (982960 megabytes) OPEN LVs: 2 QUORUM: 2 (Enabled) TOTAL PVs: 2 VG DESCRIPTORS: 3 STALE PVs: 0 STALE PPs: 0 ACTIVE PVs: 2 AUTO ON: yes MAX PPs per VG: 262144 MAX PVs: 1024 LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no HOT SPARE: no BB POLICY: relocatable
Add the new disk to the vg:
#extendvg vgdata hdisk20
The number of free PPs should be increased
bash-3.00# lsvg vgdata VOLUME GROUP: vgdata VG IDENTIFIER: 00c39a0200004c000000012bb22891c2 VG STATE: active PP SIZE: 8 megabyte(s) VG PERMISSION: read/write TOTAL PPs: 184302 (1474416 megabytes) MAX LVs: 256 FREE PPs: 61432 (491456 megabytes) LVs: 2 USED PPs: 122870 (982960 megabytes) OPEN LVs: 2 QUORUM: 2 (Enabled) TOTAL PVs: 2 VG DESCRIPTORS: 3 STALE PVs: 0 STALE PPs: 0 ACTIVE PVs: 2 AUTO ON: yes MAX PPs per VG: 262144 MAX PVs: 1024 LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no HOT SPARE: no BB POLICY: relocatable
Next, to increase the size of the LV. Oops, another error:
0516-787 extendlv: Maximum allocation for logical volume fslv01 is 122869.
this is basically the same problem, but with lv instead of vg
bash-3.00# lslv fslv01
LOGICAL VOLUME: fslv01 VOLUME GROUP: vgdata
LV IDENTIFIER: 00c39a0200004c000000012bb22891c2.2 PERMISSION: read/write
VG STATE: active/complete LV STATE: opened/syncd
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 122869 PP SIZE: 8 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 122869 PPs: 122869
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 1024
MOUNT POINT: /dump LABEL: /dump
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
DEVICESUBTYPE : DS_LVZ
COPY 1 MIRROR POOL: None
COPY 2 MIRROR POOL: None
COPY 3 MIRROR POOL: None
The max lps value should be increased in accordance to the additional space that we are planning to add. In my case it’s 500GB. To translate that to PPs, divide the volume size that you want to add with the size of your PP size, in my case it’s 512000 / 8 = 64000. Edit the max LP value with chlv -x (current PP + additional PP):
#chlv -x 186869 fslv01
The LV should be ready to be resized
bash-3.00# lslv fslv01 LOGICAL VOLUME: fslv01 VOLUME GROUP: vgdata LV IDENTIFIER: 00c39a0200004c000000012bb22891c2.2 PERMISSION: read/write VG STATE: active/complete LV STATE: opened/syncd TYPE: jfs2 WRITE VERIFY: off MAX LPs: 186869 PP SIZE: 8 megabyte(s) COPIES: 1 SCHED POLICY: parallel LPs: 122869 PPs: 122869 STALE PPs: 0 BB POLICY: relocatable INTER-POLICY: minimum RELOCATABLE: yes INTRA-POLICY: middle UPPER BOUND: 1024 MOUNT POINT: /dump LABEL: /dump MIRROR WRITE CONSISTENCY: on/ACTIVE EACH LP COPY ON A SEPARATE PV ?: yes Serialize IO ?: NO DEVICESUBTYPE : DS_LVZ COPY 1 MIRROR POOL: None COPY 2 MIRROR POOL: None COPY 3 MIRROR POOL: None
We should now be able to resize the lv using “smit jfs2” or the “extendlv” command.
Filed under: time out
You put up a good fight dad, see you on the other side
Filed under: gaming, Go Go Gadget..Stuff!! | Tags: bluetooth, gaming, logitech, M905, mouse, notebook, orochi, razer, review, wireless
I don’t have desktop anymore. I game, browse, and do works on my laptop, which I lug around almost every day. Naturally, I look for a notebook mouse to accompany the laptop, something that’s small so that it won’t take too much space on my increasingly cramped backpack.
The M905 and the Orochi represent the two opposing polars of notebook mice world. Logitech crams everything but the kitchen sink (and internal charging mechanism, we’ll talk about this later) into the tiny sleek body of the M905, while Razer built the Orochi with the sole intent of breaking speed record of the notebook mice class, figuratively speaking. Obviously, the two of them are targeted at two different market.
Filed under: Exchange, Microsoft, Windows | Tags: BIS, blackberry, block, EWS, exchange, Exchange Web Service, IIS, Microsoft, windows
Hi there,
On the first part of this (sort of) how to, I’ve shown you how to block Blackberry BIS (or any kind of services masquerading as web browser) from accessing Exchange Web Service, or EWS for short. On this one, I’ll be covering how to block BIS using IIS IP Address & Domain Restriction module. This method is preferable if you want to block certain site, or network from accessing your EWS. This method can also be used if you’re planning to provide EWS function on internal network only
First, make sure that IIS IADR module has been installed on the Exchange Server. Open the IIS manager, and see if it’s there.
Filed under: Exchange, Windows | Tags: 2010, BIS, blackberry, email, EWS, exchange, Exchange Web Service
If you’re migrating from Exchange 2003 to Exchange 2007 or 2010, you’ll find a new toy to play with. The Exchange Web Service. The EWS was meant to replace older Exchange interface such as WebDav and CDOEX, providing developers an easier way to integrate their software and solutions to Exchange system. In practice, not only software and systems, the EWS is also used for end-user apps syncing method, such the case with Blackbery phones and Outlook for Mac.
Which is bad. Why? Unlike any other end user features such as OWA and ActiveSync which you can assign on per-user basis, EWS is an organization-level feature. It’s either on for all users, or off. So for example, if you turn it on and publish it on the internet, all of your users with cheap BIS plan get to use their blackberry to sync with Exchange.
Now, there are several approach that can be used to work around this problem. The first one, is to setup a filter on EWS.
Filed under: *Nix, Ubuntu | Tags: bundle, humble, shadowgrounds, steam, trine, Ubuntu
If you’re Ubuntu user, and fans of the Humble Bundle.. err bundles, now you can get all of your Humble Bundle goodies on steam, since Valve has decided to start the open beta for Steam for Linux. Get the .deb here, and double click to install. Create a steam account if you haven’t got one.
The next step is to get the steam redeem keys for your bundle purchases. Log into your Humble Bundle account, and go to your library. Scroll all the way down to see the link to all of your purchases, and select one of the bundle that you want to redeem. The top of the next page will contain a link to your steam keys.
If you have your steam keys, fire up Steam for linux, go to Games > Activate a Product on Steam. Enter your key when asked.
One.. well.. many little problem(s), not all of the bundle’s linux games are available on Steam. Trine and Shadowgrounds for example, are available in windows and mac, but not on Steam for Linux
As you may have known, Google has pulled the plug on Picasa for linux, with 3.0 beta being the latest version available. Some of you that resourceful enough probably has realized that the linux version of picasa is basically the win32 version with bundled wine wrapper, and updating picasa to the latest version is as easy as unpackaging the installer, and replacing the old binaries and other folder contents.
Some of you may experience difficulties in signing in into your google account, with the sign in window displaying blank window such as this:

Blank login page











