Page 1 of 1

Incorrect Free Space Reported

Posted: Sun Apr 07, 2019 8:56 am
by jerryfudd81
Hi,

Oddly MakeMKV is reporting 138.5GB remaining (and dropping as its currently ripping - see screenshot) when finder reports 229.89GB. There is also nothing in the trash, any ideas on where MakeMKV is getting its information? as it keeps reporting I may not have enough space to rip the disc.

(The machine I'm using is mainly used as a server so has no requirement for a big bootable disk and only use it before moving the output file to external storage).

Image

Re: Incorrect Free Space Reported

Posted: Sun Apr 07, 2019 3:12 pm
by Woodstock
Does your machine have multiple partitions making up the file system?

If you do, it is likely that the one MakeMKV is writing to makes up only part of the free space you see.

MakeMKV asks for free space available many times during the ripping process; I've watched the free space change as I do clean-up of old files on the NAS it's writing to. Delete a TB of old rips, the free space jumps by a TB. Copy 500GB from another machine, the free space falls 500GB.

But MakeMKV is only concerned with free space associated with the partition it's writing to, because spanning partitions is rarely available.

Re: Incorrect Free Space Reported

Posted: Sun Apr 07, 2019 3:48 pm
by jerryfudd81
Thanks for the reply - its a single partition... so not sure what's going on there but as you can see the screenshot the space is available.

Re: Incorrect Free Space Reported

Posted: Sun Apr 07, 2019 7:58 pm
by Woodstock
I'm not an expert on MacOS by any stretch of the imagination, so I would have to defer to others here. I do know back when Windows first allowed on-the-fly compression of files on the drive, the free space numbers could vary wildly. I couldn't disable that fast enough!

Re: Incorrect Free Space Reported

Posted: Sun Apr 07, 2019 9:32 pm
by jerryfudd81
I'd hope I know more than most but couldn't come up with anything... its not the end of the world though so sure I can live with it until a solution presents itself.

thanks anyway