Any updates on this? It looks like the lack of space may now be causing
the registry db to break.

Worst case, you should be able to create a new larger disk image and
clone the old one onto it, or make a Time Machine backup and restore it
onto a bigger volume.

- Josh

On 2015-7-18 11:12 , Jeremy Huddleston Sequoia wrote:
> Yeah, we still have a bunch of users staying on Snow Leopard because of 
> various reasons.  Lion was the last OS that supported EFI32, so there are 
> some users who can't upgrade past Lion.
> 
> That being said, you can probably netboot to a newer OS image and use Disk 
> Utility there to resize it.  Another way of doing that if the netboot 
> approach fails is to shutdown the VM and add its disk to another VM 
> (selecting "shared" when adding it).  Then resize it in the other VM and 
> remove it (selecting "don't delete" when removing).
> 
> 
>> On Jul 17, 2015, at 13:56, Keith Dart <[email protected]> wrote:
>>
>> I did look at it and there seems to be 20GB free. That still might not be 
>> enough for some builds, I guess. I did enlarge the virtual disk by another 
>> 20 GB. But so far I’m been unable to resize the file system in the guest. I 
>> tried the disk utility and it seems to see the extra size and let me expand 
>> it by dragging a pull handle. Then I apply it, and the log entries claim it 
>> was successful. However, it is not actually resized.  
>>
>> So I guess another option is to boot into another image, such as net 
>> booting. Then try to resize the offline partition.  But there seems to be no 
>> way to do that with these VMs. So right now I’m stuck at this point. Any 
>> suggestions?
>>
>> BTW, I’m curious, does anybody still use these older OS X?  
>>
>>
>>> On Jul 14, 2015, at 21:37, MacPorts <[email protected]> wrote:
>>>
>>> #48173: Lion buildbot builder: No space left on device
>>> -----------------------------+---------------------
>>> Reporter:  ryandesign@…    |      Owner:  admin@…
>>>     Type:  defect          |     Status:  new
>>> Priority:  Normal          |  Milestone:
>>> Component:  server/hosting  |    Version:
>>> Resolution:                  |   Keywords:
>>>     Port:                  |
>>> -----------------------------+---------------------
>>> Changes (by ryandesign@…):
>>>
>>> * cc: jeremyhu@… (added)
>>>
>>>
>>> Comment:
>>>
>>> This problem did not appear again for a few weeks and I thought maybe it
>>> was mysteriously resolved (as the disk space shortage on the packages
>>> server was mysteriously resolved in #48174), but Jeremy H reported that
>>> the issue [https://lists.macosforge.org/pipermail/macports-
>>> dev/2015-July/031072.html resurfaced Sunday] when building a large port
>>> (clang-3.7). Keith, can you please respond to this ticket in some way?
>>> Thanks.
>>>
>>> -- 
>>> Ticket URL: <https://trac.macports.org/ticket/48173#comment:1>
>>> MacPorts <https://www.macports.org/>
>>> Ports system for OS X
>>
> 
> 
> 
> _______________________________________________
> macports-dev mailing list
> [email protected]
> https://lists.macosforge.org/mailman/listinfo/macports-dev
> 

_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev

Reply via email to