| Latest revision |
Your text |
| Line 52: |
Line 52: |
| | | | |
| | I have highlighted the relevant text to match. You can see that this machine is running the latest ZFS, and is one commit behind the latest SPL. | | I have highlighted the relevant text to match. You can see that this machine is running the latest ZFS, and is one commit behind the latest SPL. |
| − |
| |
| − | If you make a small local change to the code then this technique will not work. One workaround for that is to edit your file(s) and commit them in your repository clone, that way it will have a commit id.
| |
| | | | |
| | == Best practices == | | == Best practices == |
| Line 104: |
Line 102: |
| | '''A)''' Yes. O3X can import pool version 8, which means it can import MacZFS pools. | | '''A)''' Yes. O3X can import pool version 8, which means it can import MacZFS pools. |
| | | | |
| − | ===Q) Do HFS-only applications such as Photos, iCloud Drive and macOS Server work on ZFS?=== | + | ===Q) Do HFS only applications such as Photos, OSX server and others work on ZFS?=== |
| | '''A)''' Sometimes. Apple codes some software to only work when stored on HFS. We can't change that. We have provided a property that causes ZFS filesystems to identify themselves as a HFS when enabled. We are unable to guarantee that the application will work 100% correctly as HFS may have specific behaviours that the application depends on, and ZFS may not behave identically. | | '''A)''' Sometimes. Apple codes some software to only work when stored on HFS. We can't change that. We have provided a property that causes ZFS filesystems to identify themselves as a HFS when enabled. We are unable to guarantee that the application will work 100% correctly as HFS may have specific behaviours that the application depends on, and ZFS may not behave identically. |
| | | | |
| Line 113: |
Line 111: |
| | | | |
| | ===Q) Can Time Machine backups be stored on ZFS? === | | ===Q) Can Time Machine backups be stored on ZFS? === |
| − | '''A)''' Yes. It is possible to host a TimeMachine backup within a SparseImage on ZFS, or an HFS formatted ZVOL On ZFS. See: https://openzfsonosx.org/wiki/Time_Machine_Backups | + | '''A)''' Yes. It is possible to host a TimeMachine backup within a SparseImage on ZFS, or an HFS formatted ZVOL On ZFS. |
| − | | + | |
| − | ===Q) Updating crypto to 2.0 ===
| + | |
| − | '''A)''' If you go from 1.9.4 (or earlier) and use crypto, you will get "mount returns -1". This is due to missing
| + | |
| − | features userobjquota, groupobjquota and projectquotas. The pool will need "zpool upgrade" before you can mount it.
| + | |
| − | Please remember this means you can not go back to 1.9.4, as with all pool upgrades.
| + | |
| − | | + | |
| − | ===Q) Updating crypto to 2.0 from earlier 2.0-rc ===
| + | |
| − | '''A)''' There was a few early releases of 2.0-rc, where the MAC was calculated incorrectly, and you will see:
| + | |
| − | rpool/crypt:<0x0>
| + | |
| − | However, issuing "zpool scrub" will clear this issue (as it re-computes the MAC).
| + | |
| − | | + | |
| − | ===Q) Uninstalling on Big Sur and later ===
| + | |
| − | '''A)''' Unfortunately, macOS from BigSur has a tendency to "hold on" to kexts, and here is the best way to make sure the kext is not loaded:
| + | |
| − | Boot into recovery mode
| + | |
| − | Launch Terminal
| + | |
| − | # kmutil trigger-panic-medic --volume-root /Volumes/<YourVolumeName>
| + | |
| − | As in "/Volumes/MacintoshHD" or similar.
| + | |
| − | reboot normally.
| + | |
| − | trigger-panic-medic will remove all 3rd party kexts, so you need to "Approve" any kexts
| + | |
| − | you want to keep, just make sure to skip zfs.kext.
| + | |
| − | Clean up all files:
| + | |
| − | # sudo rm -rf /Library/Extensions/zfs.kext /usr/local/zfs/
| + | |
| | | | |
| | == Limitations == | | == Limitations == |
| Line 143: |
Line 119: |
| | | | |
| | ===Q) Can I boot my computer off of O3X?=== | | ===Q) Can I boot my computer off of O3X?=== |
| − | '''A)''' Yes. See https://openzfsonosx.org/wiki/ZFS_on_Boot | + | '''A)''' No. O3X cannot be used as your main system partition. |
| | | | |
| | ===Q) So if I use O3X, that means I don't need to back up, right? === | | ===Q) So if I use O3X, that means I don't need to back up, right? === |
| Line 150: |
Line 126: |
| | ===Q) Can TimeMachine backup the contents of a ZFS volume? === | | ===Q) Can TimeMachine backup the contents of a ZFS volume? === |
| | '''A)''' No. We believe that when "Issue 116" is resolved it may be supportable. At the present time TimeMachine excludes ZFS filesystems from the list of available backup targets. | | '''A)''' No. We believe that when "Issue 116" is resolved it may be supportable. At the present time TimeMachine excludes ZFS filesystems from the list of available backup targets. |
| − |
| |
| − | ===Q) How does auto-import work ? ===
| |
| − | '''A)''' Auto-import on boot is handled by Launchd, from the file '''/Library/LaunchDaemons/org.openzfsonosx.zpool-import-all.plist'''. Which executes the script
| |
| − | '''/usr/local/libexec/zfs/launchd.d/zpool-import-all.sh''' to import files. You can unload the plist, or if you want to temporarily stop auto-import, simply comment
| |
| − | out the line '''"${ZPOOL}" import -a -d /var/run/disk/by-id''' by placing a '''#''' in front of it.
| |
| − |
| |
| − | On newer versions (tested on 2.1.0) the script calls '''/Library/LaunchDaemons/org.openzfsonosx.zpool-import.plist''' which runs the command to import it upon boot. If you wish to take advantage of naming the physical drives by their path, which generally shouldn't change, edit this file and change '''<string>/var/run/disk/by-id</string>''' to '''<string>/var/run/disk/by-path</string>'''
| |
| − |
| |
| − | ===Q) I can't see my pools? ===
| |
| − | '''A)''' First make sure that '''diskutil list''' will show the disk(s) used in your pool. If not, you have a hardware and/or OsX problem to solve. Second step is running '''zpool import''' and possibly '''zpool import -d /dev''' to make ZFS inspect all disks on your system, looking for pools. The command will list any pools that it can find, and the state they are in, except for pools already imported (You can run '''zpool list''' to display the imported pools). After that, you would run '''zpool import poolname''' to import the pool, where ''poolname'' is replaced with the name of your pool. If you need further assistance, ask on the forum, irc, or, in the case of panics, create a ticket under the github repository.
| |
| − |
| |
| − | ===Q) Auto-import fails after Catalina? ===
| |
| − | '''A)''' System Preferences -> Security & Privacy -> Full Disk Access by allowing bash. (bash used by auto-import script, change to 'sh' for lingon.)
| |
