I also added a startup script to my system: hdiutil compact Torrents.sparsebundleįirst command will reclaim the unused diskspace, while second will automatically mount the image. It works very well, especially when you select only a few files in a big torrent. Setup your favorite torrent client to use the volume mounted called "Torrents repository" as temporary repository, I suggest to set it up so that completed files would be moved out of the image (to Downloads folder for example). Then double click Torrents.sparsebundle image just created to mount it. Gordon Davisson explanation was enlightening: this is how I am using sparsebundle images as a torrents download directory.įirst of all create the image (I set it to 50GB, but any size would work) hdiutil create -size 50g -type SPARSEBUNDLE -nospotlight -volname "Torrents repository" -fs "Case-sensitive Journaled HFS+" Torrents.sparsebundle For instance, Mac disk images have supported compression roughly forever, but native support for compression wasn't added to HFS+ until OS X v10.6. As far as the outer filesystem is concerned, the image file is just a (non-sparse) sequence of bytes.īTW, the image mounter can also add other features that the filesystem alone doesn't deal with. The image mounter handles sparse mappings (and AIUI only between/beyond files, not within them), but that doesn't imply that the other layers (the filesystems) can. These are then mapped (by the image mounter) to bytes in the disk image (file), which are then mapped (by the outer filesystem) to bytes on the actual disk. When you're using a disk image, the mapping is quite a bit more complicated: you have the bytes in the file being mapped (by the inner filesystem) to bytes in the (virtual) disk. A sparse file is one that has gaps in its sequence of bytes, and a filesystem that supports this will skip those missing bytes when it maps the file to disk. HFS+) handles mapping the sequence of bytes that make up the file into a sequence of bytes on disk. If you're storing a file "directly" on disk, the filesystem (e.g. If there was something about this in the forum before, i didn't find it while searching.It's because the sparseness is handled at a different level of abstraction for a sparse image vs. but my question here is more about the backup/recovery capabilities if i only have the sparse bundle from superduper. in the current instance, i have more options to explore since i moved drives around and still have access to the original drive. I am trying to figure out both my long term approaches and what i need to do to get things working in this instance. My question is how to backup and restore with APFS and sparsebundles made with superduper.ĭo i need to change something in SD when backing up so i can restore to APFS?ĭo i need to do something different to restore from a sparsebundle to an APFS formatted drive? so the original and the new drives had the same format and same OSes. the new SSD is also on 10.14.6 and is formatted as APFS. the original partition that i backed up was on 10.14.6 and the drive was formatted as APFS. I'd made the sparsebundle backup onto one of my external drives a week ago before having my internal drive swapped out for a new SSD. i didn't see anything else searching the forum that seemed relevant when searching for APFS. but i didn't see something that would help me there. I read the post on the forum "restoring to new APFS from HFS+ sparsebundl". i contacted apple support, but they won't help since my mac is passed the apple care date. i didn't get a screenshot, but the error said something to the effect that it can't restore from an HFS+ disk image to an APFS volume. When attempting to use disk utility to restore from a sparsebundle backup of my boot partition, i saw an error message. I've run into an error message in trying to restore my OS from my SuperDuper backups that i could use some advice on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |