2088 Views 7 Replies Latest reply: Dec 16, 2010 11:22 AM by KJK555
You may have successfully increased the sparsebundle's potential capacity while failing to resize the contained partition. That seems to be what happened when I tried this myself. A resized sparsebundle containing the same files would not occupy much more space on disk than it did before.
*Provided you have a backup*, you could try the following:
Remount the image, then run Disk Utility and select the .sparsebundle (non-indented icon) in the left pane. Click on the Partition tab, and then see if you can pull down the lower right corner of the disk image partition to increase its size. If you can, then drag it to the bottom and click Apply.
Again don't try this without a backup. It may not be worth doing in any event - it's easy enough just to make a new, bigger sparsebundle and copy your stuff over.
Resizing the inner partition of a Sparse image or bundle with Disk Utility is a pain. Sometimes
it works, sometimes it fails to do anything.
iPartition does it effortlessly though.
I have been using iPartition since around april 2007 (ver 1.5.7., it's at ver 3.3.1 now).
Everything Disk utility can't do (or requires the command line to do), it can do.
Resize partitions on the fly (shrink or expand), rebuild GPT (Guid) tables. Create, resize,
make bootable, msdos (boot camp) partitions (without bootcamp). Make partitions visible
or invisible to windows, format fat12,16,32, ntfs, etc. That's just for starters.