The first is that I'm attempting to copy a reported 924 billion bytes of data onto a drive with a capacity of 993 billion bytes, which sounds as though it should work… but it doesn't. It claims that more space is needed. Curious.
The second is possibly related to the first: on the external drive from which I'm attempting to copy the data, lots of the folders won't let me in unless I grant myself permission first (which always seems like such a stupidly pointless step; there's no verification required beyond me clicking a box. If we're really a problem, it wouldn't let me do it at all, so why issue the non-challenging challenge…??).
The interesting thing about this second one is that the folders which I “don't currently have permission to access” report their size as 0 bytes until I give myself permission to access them.
And there's lots of these folders.
Experimenting: after giving myself access to a few, the reported size of the whole parent directory is now 932 billion bytes! So the stupid machine is reporting an artificially-low byte-count simply because it thinks the folders it “doesn't currently have permission to access” contain 0 bytes!
Then, for unknown reasons, these restrictions disappear when the data is copied to another location, and it turns out that the data is actually much more voluminous than reported.
What the zark am I supposed to do about that…?
I've tried changing the permissions so that the computer I'm logged into has full read\write access, but it doesn't seem to apply that to sub-directories, and there's no option to force that. After doing this step, there are still folders which I “don't currently have permission to access” and they're still reporting their size as 0 bytes.
It seems I might have to click each folder individually and “click continue to permanently get access to this folder”.
Wot a load of old zark.
1303
It seems I can do this entirely using the keyboard, only using the down-arrow and enter keys. Still tedious, and seems like something I could outsource to Homer's stoopid bird.
I can't believe I'm living in the year 2025, in the time of ever-more powerful “AI” nonsense, and I'm doing this zarking stuff manually…
1432
(Some time, and a break for lunch later…)
I think I've gone through all the folders and sorted access.
…then I found out that archive files were behaving similarly, and they don't give up access so easily. I think I might be able to just copy them across and back and that might remove the permission nonsense…?
But anyway: just doing the folders has upped the data volume total to 1.056 trillion bytes, which is why it wouldn't fit on the 931 billion-byte hard-drive.
Right, so the archive files have copied across and I can indeed access them straightforwardly in their new home; now to copy them back (having moved the originals elsewhere temporarily) and see if the easy access holds up…
In terms of the issue of not having enough space to back-up this TEMP folder of things to sort, I think I'll start by just going through it and ruthlessly deleting a load of stuff I definitely don't want or I can check I have elsewhere already.
1502
Much deleting of duplicated data has been done, and the reported size of the directory has come down to a ‘mere’ 807 billion bytes, which should, even given more permission-shenanigans, fit on the 931 billion-byte hard-drive.
Blimey, that was 20% of that unsorted data, and it's just gone. How much other wasted space have I got lying around…? (My backing-up and copying strategy is hugely disorganised, so maybe don't answer that.)
1544
I'm starting a similar procedure on the other old desktop (Big Box) and it's going slowly so far. It may not be the latest machine, but it shouldn't be working as slowly as it is. Any major copying or deleting operation seems to flood its memory and even the mouse movements become jerky & broken.
And just when I was marvelling how much quicker it was to copy stuff onto a computer whose HDDs are connected via sata rather than usb (PavNAS)....