Symlinks created in MacOS do not work in windows, however windows is capable of creating symbolic links of its own, which likewise work only on windows, and also only on NTFS.
#SYMBOLICLINKER MAC LEGIT SOFTWARE#
Otherwise if there is a reason it must be Mac formatted, there are also paid software options to provied support for HFS drives in Windows, so one way or the other you can access the material on the mac drive on your windows machine. So then, as long as you take this corruption risk in to account, AND HAVE OTHER, SAFER BACKUPS IN PLACE THAT AREN'T BEING REGULARLY ACCESSED BY EDITORS, my anectdotal experience is that exFAT has worked perfectly well for editing with no increased incidence of issues compared to any other filesystem. exFAT has drawbacks in reliability, and is reputedly more likely to have corrupted data (for example if something happens to interrupt a file transfer in progress) than NTFS or HFS+, I mention this because it would be bad not to disclose the risks however I'll also note that, you're calling this a 'backup' drive and since you're handing it off to editors there's presumably several backups of that backup that are left inactive specifically just to store the data and not be messed with. But I read your second post about your use-case and unless I've misunderstood what you're trying to do then I think I can advise you what steps to take.įor the first problem, that of mac drives on windows machines, Windows doesn't support HFS drives natively, however, if you haven't already chosen what drive to use and haven't already begun your back up process before reading this, then you can use the option of formatting the external drive to the exFAT filesystem (rather than HFS) which will be accessible to both windows and MacOS. Hdiutil create -nospotlight -size 8tb -type SPARSEBUNDLE -volname "bkp_WM_S3_Imports" -fs "Case-sensitive Journaled HFS+" /Volumes/WM3_Edit_Bkp3/bkp_WM_S3_Imports.sparsebundleĬhuckkahn, in direct response to your first question, to my knowledge - no. sparsebundles are smaller than the 8 TB ones I created. Update: I think I see the reason: the Create Disk Image app defaults to 10 GB and so its. Hdiutil create -size 8tb -type SPARSEBUNDLE -volname "bkp_WM_S2_Masters" -fs "Case-sensitive Journaled HFS+" /Volumes/WM3_Edit_Bkp3/bkp_WM_S2_Masters.sparsebundle sparsebundle file is 59.6 MBĪlso, how do I create a proper SBD in the OS X Terminal? I looked at the options in the hdiutil command and they seemed quite numerous: sparsebundle file is 1.51 GB.Ģ) CreateDiskImage app - also set the SBD size to 8 TB and the size of the. Comparing ways to create Sparse Bundles.ġ) Disk Utility - I set the SBD size to 8 TB and the size of the.
0 kommentar(er)
