Oracle SQL Complications With Multiple Triggers
I am generally opposed to triggers.  They have their place but surprising behaviour, when you do one simple thing and the change ripples out across the world, will give you headaches later.

Instead of having storage_size and memory_usage on the users table, how about creating a view that displays the data you are looking for?  Then you don't need triggers at all.