Please let me know if you see any error messages.
diskutil cs resizeStack 7D2AB070-B558-4788-BD0F-ECD835245C2C 3DDE5754-7274-4D58-AED2-EF28CC6A28AF 2200g fat32 BOOTCAMP 300g jhfs+ OSX-Remainder 1900g
Here is the syntax/help and you can see what is being done.
part1Format = fat32
part1Name = BOOTCAMP
part1Size = 300g
part2Format = jhfs+
part2Name = OSX-Remainder
part2size = 1900g
lvUUID = 7D2AB070-B558-4788-BD0F-ECD835245C2C (This is "Macintosh HD")
pvUUID = 3DDE5754-7274-4D58-AED2-EF28CC6A28AF (This is disk1s2)
Usage: diskutil coreStorage resizeStack
lvUUID|MountPoint|DiskIdentifier|DeviceNode [pvUUID] size
[part1Format part1Name part1Size part2Format part2Name part2Size
part3Format part3Name part3Size ...]
Resize both a logical volume and one of its underlying physical volumes in a
single operation. A single physical volume is always chosen for the underlying
shrink or grow, even if the logical volume's logical volume group is backed by
more than one physical volume. If you do not specify a particular physical
volume, then one is chosen for you. Note that if this is a grow operation,
this verb is limited by the physical volume's partition's room to grow.
Specifying zero as the size asks for an "automatic" grow-to-fill operation.
If this is a shrink operation, you can optionally request that new partitions
be created in the newly-formed free space gap in the partition map.
Again, note that this only resizes one of the underlying physical volumes; if
you need more sophistication in managing your topology, you should use the
separate physical and logical volume resize verbs.
Example: diskutil coreStorage resizeStack
11111111-2222-3333-4444-555555555555 10g JHFS+ New 1g