OK, shrinking is not supported, but the option --force has been removed from vmkfstools? No other way to go from a 6 GB vmdk to 4 GB?

Actually, my problem has another reason: First I extended the 4 GB vmdk to 6 GB, because of vm size problems. But I also had created 2 snapshots. After the extending, the vm doesn't start, it starts from the extended original disk, though, but then I have lost all my changes.

So the most important question is: How can I get out of this difficult situation, without losing any changes?

bk

Double bummer now The procedure worked, but before you gave me the steps I already had started the disk up under a new vm.

After your steps my verdict is: cannot open disk etc.. or one of the snapshot disks it depends on.
Reason: The parent virtual disk has been modified since the child was created.

Anyway, I am sure your procedure would otherwise have helped me out.

Have a nice weekend!

bk