Disk Image Resizing

I have created a dmg disk image of 100mb. It is now full and won’t allow me to put any more files on it. I would appreciate knowing how to: 1) Delete files from the disk image. At present, every time a try to send any files to trash, it says that it is not possible and that the files/folders cannot be deleted. 2). How to increase the capacity of the disk image. Is it easier to create a new disk of a larger capacity or is there a simple way of increasing the size? I have TM operating from a 500 Gb hard drive. Thanks for your help. Cheers. And a Happy New Year to you all from sunny Bangalore!

Launch the Terminal app in /Applications/Utilities/, copy & paste this command into the window that pops up, hit the return key until you get a beep, and type a q and hit the return key:
*man hdiutil*
Now, search for resize and see how to do that. Do note that a sparse disk image will grow to fit the data. Alternatively, launch Disk Utility and search for *sparse disk image* which should bring up a hint on how to resize one.

Similar Messages

I've resized disk image, but it still won't accept new files

Hi! I made a dmg and put files in it. It filled up, so I resized it from the toolbar in disk utility. The icon indeed has the new size (according to Get Info), but as soon as I open it it reverts to the old size and it won't let me put in any more files. Help anone?

the procedure would be quite simple. start disk utility and go to file menu->new-> blank disk image. set it to be a sparse image or a sparse bundle disk image. and specify its max size manually. there are some other parameters in the disk image creation popup but you can leave them as default. then the image will be created and mounted on the desktop. open it and also open your old dmg. select everything in the old dmg and drag it over to the new sparse image. once it copies unmount the old dmg and trash it.

Encrypted Disk Image Won't Partition After Resize

Hi,
I have a 10 GB encrypted disk image on my macbook (type OS Extended (journaled)). I've pretty much filled up the space so I want to resize. I go into disk utility with the disk unmounted and 'Resized' it to 20GB. Then I mount it and go into the Partition tab. I drag the corner all the way down to fill up the space and hit Apply. It goes through the motions without error but it does not actually extend the partition to the resize. On the right next it then says something to the effect that the disk is read only and cannot resize the partition. The write status is read/write until I click apple....then it switches to 'Unmounted, read-only'. Any ideas on how to fix this? It's driving me crazy. I can provide screenshots when I'm home from work if necessary.
Thanks
Nick

Here are some screenshots of before and after I try to partition (after the resize):
After attempting to resize the partition it says 'The disk is not writable and can't be partitioned' and 'The disk is too small to contain partitions'. The disk write status also changed to read only. Doesn't make sense to me...anyone know how to fix this?
Thanks

Can you resize a encrypted disk image on a sparsebundle disk image?

I created a 50GB encrypted sparsebundle disk image on my desktop. I named it BOB and also named the encrypted disk image BOB.
It's now full.
I've just made it 60GB with Disk Utility.
I opened it but on trying to copy a 4GB file into it, I got a message saying my sparsebundle disk image is too small.
Note: Disk Utility says the following:
BOB sparsebundle is 61.4GB
mounted volume BOB is 52.1GB
Hope that's clear.
Any help would be most appreciated.

I created a 50GB encrypted sparsebundle disk image on my desktop.
hdiutil resize -size 60g BOB.sparsebundle
Result: "resize failed. File or directory does not exist"
You need to tell hdiutil where to find the target BOB.sparsebundle file. You could either specify a relative or absolute file path in the command itself, or else you could first change the current working directory to the Desktop. So if you wanted to pursue using Terminal, the second way would be to enter this command:
cd ~/Desktop
and then try the same hdiutil command again.
I'm not familiar with the hdiutil command, and I don't know if the above would work. My own feeling is that trying to manipulate an image file by experimenting with hdiutil entails a risk of corrupting the image file and losing its contents, and it is therefore essential to back up the image file first. But if you are going take the time and space needed for a backup, you might as well instead just create a new, empty 60GB (or larger!) sparsebundle disk image, and copy the contents of your old disk image into the new one. This would not involve any risks, and you'd end up with the larger disk image that you wanted. You could then delete the original, if you wished.

Ways to implement image resizing using plug-ins?

Hi Photoshop developers,
I'm a developer with a few Photoshop filter and selection plug-ins under my belt, and I have a good understanding of the SDK and tools and suites it provides. My next project is an algorithm for enlarging/resampling images to different pixel dimensions. I'm wondering if anyone has any suggestions for or experience with the best combination of plug-in types to implement this.
Clearly, I can't just write it as a filter plug-in, since there is no way to change the image dimensions from within a filter.
I'd like the resized image to remain within Photoshop (as a new window or in the original one), so an export plug-in on its own is not sufficient.
Import plug-ins seem promising, since they allow the creation of a new document of the required size. However, as best I can tell from the Photoshop 6.0 SDK documentation, import plug-ins cannot access the image data from other open documents (or even the clipboard), nor do they provide any support for channel ports and the Channel Port suite.
My best idea at this stage is to create an export plug-in to provide the user interface and calculate the resized image, and then an import plug-in to import the resized image back into a new window. (I'm supposing a further automation plug-in would then be written to perform this export/import sequence.) The difficulty I see with this approach is how to communicate the resized image data between the two plug-ins. Since the resized image will potentially be very large, the ideal solution would be to store it in channels managed by the Channel Ports suite. However, I cannot see how the channel ports created in the export plug-in could be communicated to and used by an import plug-in. The alternative would be for the export plug-in to save the resized image to a temporary file on disk, however this seems unnecessary.
So, my questions, specifically, are:
a) Is it possible to create new channels using the Channel Ports suite (sPSChannelPorts->New()) in one plug-in, and have those channels persist to be used in another plug-in?
b) If so, how would the channel ports be communicated between the plug-ins?
c) Alternately, are there any alternative architectures available for implementing an image-resizing algorithm using the plug-in types that are available for Photoshop developers.
Any responses would be greatly appreciated; I know this is a low-traffic forum...
Thanks,
Matthew.

I would make an automation plug-in and a filter plug-in. 1) Run the automation which runs your filter to gather current image information 2) Create a temp file of the new document 3) Make a new document 4) Call the filter again to reload the temp data on disk <[email protected]> wrote in message news:[email protected]... > Hi Photoshop developers, > > I'm a developer with a few Photoshop filter and selection plug-ins under > my belt, and I have a good understanding of the SDK and tools and suites > it provides. My next project is an algorithm for enlarging/resampling > images to different pixel dimensions. I'm wondering if anyone has any > suggestions for or experience with the best combination of plug-in types > to implement this. > > Clearly, I can't just write it as a filter plug-in, since there is no way > to change the image dimensions from within a filter. > > I'd like the resized image to remain within Photoshop (as a new window or > in the original one), so an export plug-in on its own is not sufficient. > > Import plug-ins seem promising, since they allow the creation of a new > document of the required size. However, as best I can tell from the > Photoshop 6.0 SDK documentation, import plug-ins cannot access the image > data from other open documents (or even the clipboard), nor do they > provide any support for channel ports and the Channel Port suite. > > My best idea at this stage is to create an export plug-in to provide the > user interface and calculate the resized image, and then an import plug-in > to import the resized image back into a new window. (I'm supposing a > further automation plug-in would then be written to perform this > export/import sequence.) The difficulty I see with this approach is how to > communicate the resized image data between the two plug-ins. Since the > resized image will potentially be very large, the ideal solution would be > to store it in channels managed by the Channel Ports suite. However, I > cannot see how the channel ports created in the export plug-in could be > communicated to and used by an import plug-in. The alternative would be > for the export plug-in to save the resized image to a temporary file on > disk, however this seems unnecessary. > > So, my questions, specifically, are: > > a) Is it possible to create new channels using the Channel Ports suite > (sPSChannelPorts->New()) in one plug-in, and have those channels persist > to be used in another plug-in? > > b) If so, how would the channel ports be communicated between the > plug-ins? > > c) Alternately, are there any alternative architectures available for > implementing an image-resizing algorithm using the plug-in types that are > available for Photoshop developers. > > Any responses would be greatly appreciated; I know this is a low-traffic > forum... > > Thanks, > Matthew.

Why won't Photoshop revert to earlier history state after image resize when scripted?

I've written an Applescript to automate watermarking and resizing images for my company. Everything generally works fine —　the script saves the initial history state to a variable, resizes the image, adds the appropriate watermark, saves off a jpeg, then reverts to the initial history state for another resize and watermark loop.
The problem is when I try not to use a watermark and only resize by setting the variable `wmColor` to `"None"` or `"None for all"`. It seems that after resizing and saving off a jpeg, Photoshop doesn't like it when I try to revert to the initial history state. This is super annoying, since clearly a resize should count as a history step, and I don't want to rewrite the script to implement multiple open/close operations on the original file. Does anyone know what might be going on? This is the line that's generating the problem (it's in both the doBig and doSmall methods, and throws an error every time I ask it just to do an image resize and change current history state):
 set current history state of current document to initialState
and here's the whole script:
property type_list : {"JPEG", "TIFF", "PNGf", "8BPS", "BMPf", "GIFf", "PDF ", "PICT"}
property extension_list : {"jpg", "jpeg", "tif", "tiff", "png", "psd", "bmp", "gif", "jp2", "pdf", "pict", "pct", "sgi", "tga"}
property typeIDs_list : {"public.jpeg", "public.tiff", "public.png", "com.adobe.photoshop-image", "com.microsoft.bmp", "com.compuserve.gif", "public.jpeg-2000", "com.adobe.pdf", "com.apple.pict", "com.sgi.sgi-image", "com.truevision.tga-image"}
global myFolder
global wmYN
global wmColor
global nameUse
global rootName
global nameCount
property myFolder : ""
-- This droplet processes files dropped onto the applet
on open these_items
-- FILTER THE DRAGGED-ON ITEMS BY CHECKING THEIR PROPERTIES AGAINST THE LISTS ABOVE
 set wmColor to null
 set nameCount to 0
 set nameUse to null
 if myFolder is not "" then
 set myFolder to choose folder with prompt "Choose where to put your finished images" default location myFolder -- where you're going to store the jpgs
 else
 set myFolder to choose folder with prompt "Choose where to put your finished images" default location (path to desktop)
 end if
 repeat with i from 1 to the count of these_items
 set totalFiles to count of these_items
 set this_item to item i of these_items
 set the item_info to info for this_item without size
 if folder of the item_info is true then
process_folder(this_item)
 else
 try
 set this_extension to the name extension of item_info
 on error
 set this_extension to ""
 end try
 try
 set this_filetype to the file type of item_info
 on error
 set this_filetype to ""
 end try
 try
 set this_typeID to the type identifier of item_info
 on error
 set this_typeID to ""
 end try
 if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
-- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
process_item(this_item)
 end if
 end if
 end repeat
end open
-- this sub-routine processes folders
on process_folder(this_folder)
 set these_items to list folder this_folder without invisibles
 repeat with i from 1 to the count of these_items
 set this_item to alias ((this_folder as Unicode text) & (item i of these_items))
 set the item_info to info for this_item without size
 if folder of the item_info is true then
process_folder(this_item)
 else
 try
 set this_extension to the name extension of item_info
 on error
 set this_extension to ""
 end try
 try
 set this_filetype to the file type of item_info
 on error
 set this_filetype to ""
 end try
 try
 set this_typeID to the type identifier of item_info
 on error
 set this_typeID to ""
 end try
 if (folder of the item_info is false) and (alias of the item_info is false) and ((this_filetype is in the type_list) or (this_extension is in the extension_list) or (this_typeID is in typeIDs_list)) then
-- THE ITEM IS AN IMAGE FILE AND CAN BE PROCESSED
process_item(this_item)
 end if
 end if
 end repeat
end process_folder
-- this sub-routine processes files
on process_item(this_item)
 set this_image to this_item as text
 tell application id "com.adobe.photoshop"
 set saveUnits to ruler units of settings
 set display dialogs to never
open file this_image
 if wmColor is not in {"None for all", "White for all", "Black for all"} then
 set wmColor to choose from list {"None", "None for all", "Black", "Black for all", "White", "White for all"} with prompt "What color should the watermark be?" default items "White for all" without multiple selections allowed and empty selection allowed
 end if
 if wmColor is false then
 error number -128
 end if
 if nameUse is not "Just increment this for all" then
 set nameBox to display dialog "What should I call these things?" default answer ("image") with title "Choose the name stem for your images" buttons {"Cancel", "Just increment this for all", "OK"} default button "Just increment this for all"
 set nameUse to button returned of nameBox -- this will determine whether or not to increment stem names
 set rootName to text returned of nameBox -- this will be the root part of all of your file names
 set currentName to rootName
 else
 set nameCount to nameCount + 1
 set currentName to rootName & (nameCount as text)
 end if
 set thisDocument to current document
 set initialState to current history state of thisDocument
 set ruler units of settings to pixel units
 end tell
DoSmall(thisDocument, currentName, initialState)
DoBig(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 close thisDocument without saving
 set ruler units of settings to saveUnits
 end tell
end process_item
to DoSmall(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 set initWidth to width of thisDocument
 if initWidth < 640 then
resize image thisDocument width 640 resample method bicubic smoother
 else if initWidth > 640 then
resize image thisDocument width 640 resample method bicubic sharper
 end if
 set myHeight to height of thisDocument
 set myWidth to width of thisDocument
 if wmColor is in {"White", "White for all"} then
 set wmFile to (path to resource "water_250_white.png" in bundle path to me) as text
 else if wmColor is in {"Black", "Black for all"} then
 set wmFile to (path to resource "water_250_black.png" in bundle path to me) as text
 end if
 if wmColor is not in {"None", "None for all"} then
open file wmFile
 set wmDocument to current document
 set wmHeight to height of wmDocument
 set wmWidth to width of wmDocument
duplicate current layer of wmDocument to thisDocument
 close wmDocument without saving
translate current layer of thisDocument delta x (myWidth - wmWidth - 10) delta y (myHeight - wmHeight - 10)
 set opacity of current layer of thisDocument to 20
 end if
 set myPath to (myFolder as text) & (currentName) & "_640"
 set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
 set current history state of current document to initialState
 end tell
end DoSmall
to DoBig(thisDocument, currentName, initialState)
 tell application id "com.adobe.photoshop"
 set initWidth to width of thisDocument
 if initWidth < 1020 then
resize image thisDocument width 1020 resample method bicubic smoother
 else if initWidth > 1020 then
resize image thisDocument width 1020 resample method bicubic sharper
 end if
 set myHeight to height of thisDocument
 set myWidth to width of thisDocument
 if wmColor is in {"White", "White for all"} then
 set wmFile to (path to resource "water_400_white.png" in bundle path to me) as text
 else if wmColor is in {"Black", "Black for all"} then
 set wmFile to (path to resource "water_400_black.png" in bundle path to me) as text
 end if
 if wmColor is not in {"None", "None for all"} then
open file wmFile
 set wmDocument to current document
 set wmHeight to height of wmDocument
 set wmWidth to width of wmDocument
duplicate current layer of wmDocument to thisDocument
 close wmDocument without saving
translate current layer of thisDocument delta x (myWidth - wmWidth - 16) delta y (myHeight - wmHeight - 16)
 set opacity of current layer of thisDocument to 20
 end if
 set myPath to (myFolder as text) & (currentName) & "_1020"
 set myOptions to {class:JPEG save options, embed color profile:false, quality:12}
save thisDocument as JPEG in file myPath with options myOptions appending lowercase extension
 set current history state of current document to initialState
 end tell
end DoBig

As many others here I use JavaScript so I can’t really help you with your problem.
But I’d like to point to »the lazy person’s out« – with many operations that result in creating a new file on disk I simply duplicate the image (and flatten in the same step) to minimize any chance of damaging the original file if the Script should not perform as expected.

Disk images after snow leopard

Hi all,
I recently installed SL on a MacBook Air using remote disk. The process was not smooth, with several failed installs due to dropped connections between the Air and my main MacBook Pro. It's all installed now, but every time I load up I get three disk images on the desktop labelled 'OS X'. Each one says for example '2.28GB, 1.16BG free'.
All of these can be ejected but its quite annoying to do it everytime I start up, and I assume they are taking up 2.28GB each until I eject them.
Anyone know what's going on and how I can get rid of it?
Thanks,
Ben

The problem is that you have an unneeded partition on your HD—left over from an unsuccessful install of Sno. To remove it, open ~/Applications/Disk Utility. Then, select your hard drive volume from the list on the left, and next select the "Partition" tab. You'll see the unneeded "Install OS X" partition in the diagram. Select it and press the "-" button underneath to remove the partition. Afterward, resize the Macintosh HD partition to include the space used by unneeded partition.

OSX G5 Disk Image and HDD manipulation... Help

Hello Everyone.
On the PC a program called Partition Magic, among others, that allows partition copy, resize, create, delete, etc.
I have used Mac disk utility, but I haven't found it to do what I'm trying to do.
I am looking for the same type of program on the Mac that will work on IMAGE FILES. If I image my HDD and it's 60Gb, but only 20Gb is used, then I have a lot of wasted space in my image file. I would like software to adjust the size UP or DOWN for a given image file. And no, I do not want to recreate the whole image everytime I resize it.
Would also like a program that works on the physical HDD to change the size of an existing partition without destroying it.
Thank you again,
Scott
Powermac G5 'Quad' Mac OS X (10.4.4)
Powermac G5 'Quad' Mac OS X (10.4.3)

When you select either of the two options for your camera on the left, you care going to create a disk image of your entire hard drive. If you have a 60GB camera, you will have a 60GB disk image. If your camera is totally full, this may be OK. But if your camera only has 20GB and you want to back it up to a disk image, you could be wasting 40GB.
THe solution is to create a blank disk image with a custom size (that is just large enough for what you need. Make it Read / write (R/W) format. You can mount this disk image later and drag the complete contents of your camera to it.

Deleted Disk Image but space is not available on hard drive

I was trying to share the iPhoto library across users by creating a Disk Image via Disk Utility.
It didn't go a planned as I needed more space than originally allocated. The resizing option in Disk Utility specified the Maximum Size was less than what I needed.
My next step was to delete this Disk Image, I believe I did this by selecting Edit > Delete
The Disk Image disappeared however the 80 GB never reappeared on my harddrive as available. I tried emptying the Trash but that did not correct the problem.
Any assistance would be much appreciated.

No the /Volumes folder twtwtw is refering to is at the top level of the root disk.
To see it open a Finder window and select the Go menu item
then select Go to Folder…
Now in the window that opens enter /Volumes
Then Go
the /Volumes folder will open. There should be no regular files or folders in there

Password-protected Sparse Disk Image Bundle remembered after eject

I use password-protected Sparse Disk Image Bundles to protect some files. Every now and then, when I open the image, it doesn't ask me for the password and opens immediately.
At first, I thought I may have inadvertantly agreed to save the password in Keychains. But that is not the case. After running some tests, I noticed it may take up to 3 ejects before it asks me for the password again. It seems to happen more when I modify files in the disk image, but not when I simply read files. I suspect it is not completely unmounting the image.
This is potentially a security issue. Any suggestion on what I can do short of re-ejecting images until it asks for a password again?

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.

Disk Image Creation hanging

I wanted to be able to lock certain files with a password, so I created a 2.8 GB disk image to store them in. Now that I am realizing the 2.8 GB is not enough, I'm trying to either increase it or create a second disk image that is 8 to 10 GB and then transfer the contents there.
Increasing the current image size failed. And every time I go to create a second one, it just sits at the halfway point in the progress bar. I figured some hard disk or network action was causing it to falter, so I turned all services off, disconnected the ethernet cable and tried again; same results.
Any idea?

as i explained, a regular r=disk image will take as much space on the hard drive as the max size of the image you specify at creation. this is highly inefficient. a sparse image will only take as much space as the data inside. and you can choose any max size you want. choose 300GB. you'll never reach it and so you'll never have to resize.
the difference between sparse bundle and a regular sparse image is that a sparse bundle is split in a number of bands. that makes it convenient to use when doing incremental backups with time machine. if you don't use time machine then you don't need to worry about that.

Maintaining/updating OS X disk images

Hi everyone,
I have a number of disk images here which we use for system deployment at work. We boot client machines off a Netboot server, remote in using ARD, then use Carbon Copy Cloner to re-image the local drive. These disk images need to get the latest bunch of OS X updates, need a few new applications added to them, plus a few other changes.
Is there any way I can do this easily without having to go through the effort of deploying the image onto a machine, making the changes, then re-imaging the drive? Is there a way I can boot off a disk image and make all the changes, which would then be saved in the disk image for future deployment?
Any help would be greatly appreciated.

I haven't heard of booting from a mounted disc image. Don't know if it's possible or not. How does it get mounted at boot time? That would surprise me if it is possible. Maybe over the network to another machine that has mounted it already, if you could boot from a network volume? Then you have the network bottleneck to deal with that will slow down the update/installation process a little.
Some software installers, and I think OS X updates, will allow you to install on any mounted volume that contains the OS X, even though you didn't boot from it, which should include a mounted disc image that is writable and has enough space, or automatically resizes to fit the data. (is that called a sparse image?)
One thing to be aware is that some OS X updates install a start up script to complete the installation at the next boot, so the updater/installer hasn't quite finished the job. You may have to reboot from the OS image to complete the installation of some components. Not sure if you want to deploy that initial boot image to complete the installation on all your machines before you checked it out on one machine first ... depends on the type of update if this is the case or not.
(And of course you would want to test stuff out on a duplicate copy and not risk corrupting any of your existing production disc images.)

Using Encrypted Disk Images

When I create an encrypted sparse bundle disk image it starts small an grows when I add files. When I create a sparse disk image it starts at the size I set and never grows. I understand all this however, what I don't understand is gaining FREE space again. When I delete a file I don't get back the free space on the mounted virtual drive but the disk image is still the same size! I know that filevault (which basically just places your home folder in an encrypted Sparse bundle image) some how recovers space, is this possible with other ENCRYPTED disk images as well?
Thanks in advance,
Macguy3000

A sparse image file can expand but it does not automatically contract as data is removed. I believe I remember reading a hint at MacOSXHints.com about how to resize a sparse image file.

Networked backup "sparsebundle" disk image?

Hey folks,
I have a 500GB internal drive on my PowerMac G5 that I'm using for Time Machine backups. I've set it up so my 160GB main drive does regular backups to it, and it created the standard "Backups.backupdb" folder. I have a PowerBook as well, which I also decided to backup to the same drive using AFP to connect the laptop to the 500GB drive on my desktop. Time Machine works well, but instead of backing up to a folder, it has created a disk image for my laptop that it's called a "sparsebundle" file. The image is dynamically resized as files are added to it, but I'm wondering if this is expected behavior. I can imagine the disk image would protect the laptop's backup when the drive starts getting full, so the Desktop's backups dont interfere with it, but wouldn't it also be wise to have the desktop's backups go to another disk image as well? Seems kinda strange...

That's how it works. Not sure why, but local backup disks get a Backups.backupdb and networks get a spare disk image which contain a Backups.backupdb.
It may have something to do with keeping the permissions straight. Real permissions are done by UID, not by account name. And there is no guarantee that Joe on the desktop is the same UID as Joe on the laptop.
But if the disk was written by the desktop, then the wrong UID might be applied compromising privacy and security. By creating a new disk image which is only mounted on the sending Mac, perhaps the UID problem is averted.
Just guessing though.

Time Capsule and Time Machine (Sparse Disk Image Bundle)

I just changed the HD that I use to backup TM for Time Capsule. I do not know why it is taking so long (more than 45 min) to calculate size... I took a look at TC and I found "Backups.backupdb" with no item (in TC) and a disk image called "Mac Pro’s Mac Pro.sparsebundle" right beside another dm called Mario.sparsebundle (my MacMini). Did it change from before, it used to be a folder called Backups.backupdb and inside her, folders with your computer's name? Is there something wrong? Should I stop TM?
Mario Lordeiro

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.

Disk Image Resizing

Similar Messages

Maybe you are looking for