Well, one way to do it might be to go in here. So how do I drag and drop from inside this folder to inside that folder. Then say I want to move that into the Miscellaneous folder. Like instance here I've got some folders and let's say let's look in the Docs folder here. But dragging and dropping can be tough in some situations. Now you probably know how to use Drag and Drop to move files and that's the standard way to do it. Video Transcript: A great way to move files around in the Finder is to use Copy and Paste. So it seems that for new, clean files everything is ok, but I you overwrite or append to a file, it's not.Įven weirder: when I duplicate this file, the duplicate shows correctly using 69,2MB on disk.Check out How To Copy and Paste Files In the Mac Finder at YouTube for closed captioning and more options. If I overwrite this file with the same command ''dd if=/dev/random of=testfile.bin bs=1m count=66', it incorrectly shows as '69.206.016 bytes (84,9 MB on disk)'. If I create a clean, new 66MB file with 'dd if=/dev/random of=testfile.bin bs=1m count=66' on my internal ssd, it shows correctly in Finder info as '69.206.016 bytes (69,2 MB on disk)'. I did some more tests on my own macbook (M1 Air running 12.6): This is on a late 2014 Mac Mini running Catalina 10.15.7.Įdit: This just got weirder. So.any idea what is happening here? Is there something wrong with APFS on large drives? Or is this 'by design'? There it correctly reported as being 69.206.016 bytes (69,2 MB on disk) To check if it was an OS or APFS thing, I copied this file to the internal drive of this mac (alsof APFS formatted). Now the file suddenly was 69.206.016 bytes (84,9 MB on disk) This file reported as 68.157.440 bytes (68,2 MB in disk).Īt 66 it changed. Next I tried increasing the size of the testfile by changing the count in the dd command. Inspected the file, and it reported as 1.048.576 bytes (1 MB on disk). If block size was the problem, it would report as 16MB instead of 1MB. Although this would mean something like a 16MB block size, which didn't seem plausible.īut just for testing, I created a single 1MB file with 'dd if=/dev/random of=testfile.bin bs=1m count=1'. I thought: maybe the block size on the 14TB drive is too large, so when a file is just a bit larger than an exact number of blocks, it takes a whole extra block for just a bit of data. One psd file was 68.253.265 bytes (68,3 MB on disk) on the server, but its copy on the 14TB drive was 68.253.265 bytes (84,9 MB on disk). I checked the files in this folder, and indeed, some files took way more disk space than their actual size. The folders reported as being the same size, but the 'on disk' part for some folders was larger than on the server (for example, a folder on the server reported as '512.846.824 bytes (512,9 MB on disk)' but on the 14TB drive as 512.846.824 bytes (551,6 MB on disk)) I compared the folders that where already copied, to the source folders on the server. However, when copying to the 14TB drive, it doesn't fit. The folder reports on the server as being 12TB in size. So, I'm trying to create backup of folder on a server volume to an external 14TB APFS-formatted hard drive. Edit: doesn't seem tied to large drives, but an APFS-specific problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |