News for hackers. Stuff that matters.

lundman

Cool, as someone still working with that code (a little bit still remains) thanks for your work :)
Can't comment on the original macos version, or zevo version, but you will not lose a pool by "just unplugging it" or rebooting without export.
Re:An extensive ZFS setup on MacOS on Saturday July 07, 2018 @08:43AM (#17478257)
\o/
Re:ZFSin: A Windows kernel-mode ZFS driver on Wednesday November 01, 2017 @11:24PM (#15607592)
Alas, didn't quite work. Turns out DPC's are not allowed to wait, so the first condvar we hit in zio makes us die :)
Re:ZFSin: A Windows kernel-mode ZFS driver on Sunday October 29, 2017 @08:13PM (#15582327)
Looks like I started 2017/02/08
Re:ZFSin: A Windows kernel-mode ZFS driver on Wednesday October 25, 2017 @09:42AM (#15549992)
Ah that looks interesting. I will research that once I leave SF
Re:ZFSin: A Windows kernel-mode ZFS driver on Wednesday October 25, 2017 @09:30AM (#15549910)
Just a matter of cherry-picking it in. I'll get around it it soon
Re:ZFSin: A Windows kernel-mode ZFS driver on Wednesday October 25, 2017 @09:29AM (#15549901)
Just a hobby, working on it because I want to :)
Re:ZFSin: A Windows kernel-mode ZFS driver on Wednesday October 25, 2017 @09:28AM (#15549893)
I tried that way first, but because it called the callback at different level, and ZFS grabs a mutex, it just died. Which why I changed it to spawn a taskq to wait for the callback to come back, then tell ZFS about it. So it is async right now, I'm just not happy it has to create yet another taskq to handle it, for each IO request.