On 7/23/24 06:31, Thomas Munro wrote:
> On Tue, Jul 23, 2024 at 7:37 AM Andres Freund <andres@anarazel.de> wrote:
>> [2] https://cirrus-ci.com/task/5190473306865664
>
> "Error: “disk.img” couldn’t be copied to
> “3FA983DD-3078-4B28-A969-BCF86F8C9585” because there isn’t enough
> space."
>
> Could it be copying the whole image every time, in some way that would
> get copy-on-write on the same file system, but having to copy
> physically here? That is, instead of using some kind of chain of
> overlay disk image files as seen elsewhere, is this Tart thing relying
> on file system COW for that? Perhaps that is happening here[1] but I
> don't immediately know how to find out where that Swift standard
> library call turns into system calls...
>
> [1] https://github.com/cirruslabs/tart/blob/main/Sources/tart/VMDirectory.swift#L119
I tried moving ~/.tart/tmp to the external drive as well, but that
failed -- I *think* because tart is trying to do some kind of hardlink
between the files in ~/.tart/tmp and ~/.tart/vms. So I move that back
and at least the ventura runs are working again.
</facepalm>I also noticed that when I set up the external drive, I
somehow automatically configured time machine to run (it was not done
intentionally), and it seemed that the backups were consuming space on
the primary drive </facepalm>. Did I mention I really hate messing with
macos ;-). Any idea how to disable time machine entirely? The settings
app provides next to zero configuration of the thing.
Anyway, maybe with the time machine stuff removed the there is enough space?
I guess if all else fails I will have to get the mac mini with more
built in storage in order to accommodate sonoma.
--
Joe Conway
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
