When I first starting reading I read over your literal question - the filesystem stats are not changing.
A bit of analysis.
The lsvg output says each PP (physical partition) is 256M (byte) - so 4 of these would be 1 GByte - and 40 would be the 10GByte that du is reporting.
Since 482 are already allocated - chfs simply does the expansion in place - so the lsvg/lslv output should not be changing.
At this point, as pointed out earlier that you have 482 PP in one listing, and 483 PP in another - whoever is running these commands (for you) is not giving you data "as it happens" - short form - I see too many "mistakes" in the data to provide a reply "to the data presented to us".
More analysis and guessing:
Quote:
sapep101dr(root):/home/root>chfs -a size=+512M /oracle/EP1/sapdata1
Filesystem size changed to 253231104
chfs looks at the data in /etc/filesystems (aka LVCB/VG info) and updates that. If another filesystem is mounted over that mount point then df will tell what is mounted over that mount point.
Getting back to the data above - the 2532231104 is in 512 byte blocks. That is roughly 120.75 GByte - and if we multiple 120.75 * 4 (i.e. 4PP per GByte we get 483 PP)
My guess is that
chfs is working as it should, but something else is mounted over
/oracle/EP1/sapdata1