![]() I've set up my Mac with a ZFS dataset mounted as my Desktop folder, because Monterey unfortunately misbehaves when the entire Home folder is a separate volume no matter what filesystem is used. I have found no other solution to reliably and passively back up my whole machine over my cell phone's spotty hot spot connection with any degree of reliability. I have to say, I have been using your Big Sur arm64 2.1.0 package on my M1 Max MBP (which, of course, must run Monterey or newer) for the past year, and it has been spectacular. Jörgen! Thank you so much for your efforts here! Other devs are also helping, which has been great. I also work on the Windows port, so I try to share my time between them. The biggest concern is really that Apple can just ban VFS kext whenever they want, and then there will be no more ZFS, unless they provide some other API. The main focus has been to try to upstream it into OpenZFS, so it wont be "separate". You can not keepsyms=1, you can not boot verbose.īut, this week, we have M1 stable(r) again, and a. You can not run M1 in VMs (recent change, you can but can't load kexts), you can not run variant kernels (development/debug), you can not lldb work (beyond printing the logs, show stack). M1/arm64 has caused some issues, new platform of course, but mostly due to the lack of development support. You can run 2.1.99 if you want to be at the edge. pkg installers, so latest there should be 2.1.0. ![]() The Intel version is doing rather well, and generally we just sync with upstream. I might be able to shed some light on it. In contrast the Windows build is much worse and cannot be trusted with data.Ĭurrent ZFS 1.9.4 features that can be enabled with 0.8.6 (and later) I was really happy about OpenZFS being available on MacOS when I needed it, it was a life saver. As long as you have the data backed up somewhere safe, I would not be too concerned. Then perhaps don't update feature flags on the pool anymore to ensure it stays compatible. I'd set up the pool on a linux distribution with a current openzfs version and see if it can be imported on MacOS. No idea if it still works at all due to requiring a kext and Monterey not being particularly custom kext friendly. On my current M1 Mac with Monterey I have not tried it and I am unsure if it's even compatible at all with Apple Silicon yet. It specifically used OpenZFS because I needed to do TM backups on two slightly broken drives, and ZFS was able to handle the constant resilvers, scrubs, errors, and bringing a dropped out drive back online with no crashes, kernel panics or anything. I have last used it with Catalina on an Intel Mac and it worked perfectly well - I needed features beyond what APFS can do, and the simple mirror I set up worked well. Half the point of asking questions in a public sub is so that everyone can benefit from the answers-which is impossible if you go deleting everything behind yourself once you've gotten yours. If I catch anybody else deleting their question and all their comments on it immediately after getting an answer, they're getting an instant banhammer. But please don't flame people for not using your own personal One True Platform. If there's useful information about a difference in implementation or performance between OpenZFS on FreeBSD and/or Linux and/or Illumos - or even Oracle ZFS! - great. If your post or comment gets hidden, send modmail and we'll take a look. NOTE: sometimes Reddit's auto-spam system flags links it shouldn't. This isn't an issue we usually have trouble with, so let's just keep not having trouble with it. BUT, only if it's materially useful to answer a question, or offer information, in some sense other than "this will get people to give me money." It's fine to link to youtube videos, blog posts, what have you. If you think somebody's wrong, you can say that without casting aspersions or being super sarcastic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |