|
I ordered a 2TB WD Blue SN570 for my 2015 2.2ghz 15" MBP a couple weeks ago. Apparently on MacRumours this model of NVME drive is listed as being problematic with some 2013-2014 Macbooks, and I purchased the drive without having known that the jury was still out on 2015 models as well. That said, I installed Catalina as normal, transferred everything over from a 1TB Time Machine, and everything seemed to go off without a hitch, but I've noticed lately that Finder tends to be incredibly slow to notice changes in available free space on the drive itself. For example, let's say I'm using 1TB of space. If I delete 300GB and empty the trash, it will still say I'm using 1TB of space and won't update to reflect that it should say I'm only using 700GB of space for hours. Is there a reason this might be happening, and any remedy? I've tried using Google to search "macbook slow available free space refresh" but that's a terrible way to frame it so my searches only bring up unrelated questions about system slowness rather than storage related issues. Example: Notice how I have simultaneously 800GB or 1200GB free depending on where I look. I deleted 400GB of files hours ago. One part of the system knows this, the other still hasn't figured it out. The trash is empty. What the gently caress is going on here? I'm trying to use a 1TB external drive as a Time Machine backup disk, and because one part of the operation thinks I'm only using 800GB it lets me start the time machine, but then it gets to 1000GB transferred and says "Whoops, we've run out of space and this backup was a failure. Get a bigger drive, idiot." But I know for a fact it'll still work if I'm actually using less than 1TB, which I thought I was, but apparently am not. I feel like I'm taking crazy pills here. Alternately, how can I partition this 2TB APFS drive right down the middle to have hard 1TB limits per each container so that I can use my 1TB external as a time machine for the boot container, rather than having two
|
# ? Dec 30, 2022 07:04 |
|
|
# ? May 2, 2024 20:37 |
|
XYZAB posted:What the gently caress is going on here? IDK but I'd be curious if a reboot fixed the issue immediately rather than waiting hours. That could narrow it down slightly.
|
# ? Dec 30, 2022 22:55 |
|
Zogo posted:IDK but I'd be curious if a reboot fixed the issue immediately rather than waiting hours. That could narrow it down slightly. Reboot did not fix it, so I said gently caress it and had other things to attend to yesterday anyway, and when I check today, it's fine again: Edit: killall Finder and/or totalfinder seem to force a recheck that fixes the problem, but it's still confusing why it's happening at all. XYZAB fucked around with this message at 00:25 on Jan 7, 2023 |
# ? Dec 31, 2022 22:12 |