Then I wonder, why affecting 1.9G to /tmp, or 1.8G to /var and only 27M to /storage?
Not really mentioned here, but /tmp and /var are "tmpfs" filesystems. Which is basically like a ramdisk and is not persistent storage or using any real disk partitions.
There is a safeguard in the resize script that will not do the resizing if the /storage partition already has some key folders. Where things go wrong is when you re-image and decide to copy files over and then recover files from a backup before first boot. This is likely your situation, and it requires a manual partition resizing & filesystem resizing.