Adventures with v2.0.1 on OS X 10.9

New to OpenZFS on OS X (Or ZFS in general)? Ask your questions here!

Adventures with v2.0.1 on OS X 10.9

Postby Wowfunhappy » Mon May 31, 2021 10:25 am

Hello! I just upgraded from OpenZFS on OS X v1.9.2 to v2.0.1. I completely removed 1.9.2 first using its uninstall script, rebooted, installed 2.0.1, and rebooted again!

Upon rebooting, I noticed that my pool had not been imported automatically. So I ran sudo zpool import in the Terminal, which resulted in:

Code: Select all
~$ sudo zpool import
   pool: Archive
     id: 5128411350665296666
  state: FAULTED
status: One or more devices are missing from the system.
 action: The pool cannot be imported. Attach the missing
   devices and try again.
   see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-3C
 config:

   Archive                                         FAULTED  corrupted data
     mirror-0                                      DEGRADED
       media-081EF5CC-C6EA-3345-8E76-791B22FA0C5F  UNAVAIL  cannot open
       PCI0@0-SAT0@1F,2-PRT0@0-PMP@0-@0:0          ONLINE

   pool: Archive
     id: 256552084356463370
  state: ONLINE
status: Some supported and requested features are not enabled on the pool.
 action: The pool can be imported using its name or numeric identifier, though
   some features will not be available without an explicit 'zpool upgrade'.
 config:

   Archive                                         ONLINE
     mirror-0                                      ONLINE
       media-A16DF3F1-7F5C-F34F-BC64-7B22892E23FF  ONLINE
       media-D397764E-706E-FF40-869C-D1DB9CEB4E6C  ONLINE


Suffice to say, I did not create two pools with the same name. There should only be one, called "Archive".

Running sudo zpool import 256552084356463370, but the "ghost" version, with id "5128411350665296666" is still there when I run zpool import, and it appears to be preventing the real pool from being imported automatically upon reboot.

Is this a Mavericks-specific issue? Nodarkthings mentioned issues with autoimport on 10.9 over here, but I couldn't tell from the information provided whether he was running into the same problem or something else.

Would I be better off going back to 1.9.2 for full Mavericks compatibility? I don't strictly need any of the new features.

Alternately, should I try just wiping the drives and recreating the pool? I have a backup NTFS drive I can use to restore my files. This would leave me with n - 1 copies of my data for a few hours, which isn't ideal, but it would probably be fine.

Thanks!
Last edited by Wowfunhappy on Tue Jun 01, 2021 5:57 am, edited 1 time in total.
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby Wowfunhappy » Mon May 31, 2021 2:41 pm

Because the "ghost" pool was said to be on PCI0@0-SAT0@1F,2-PRT0@0-PMP@0-@0:0, and because that was the device tree address of /dev/disk2 according to Disk Utility, I figured the problem had to be on /dev/disk2. Because this is a mirrored pool and the files are backed up elsewhere, I decided I'd just wipe disk2 in Disk Utility, and let ZFS resilver the pool.

I was correct in that wiping disk2 made the ghost pool disappear. However, I can't seem to replace the disk so it resilvers:

Code: Select all
$ sudo zpool replace Archive /dev/disk2
internal error: out of memory


Mavericks bug? I know 10.9 wasn't well-tested. :)

Edit: Whoops, that was dumb. So when I wiped the disk in Disk Utility, I'd selected Apple Partition Map because the idea was to let ZFS fix it. Setting it to GUID partition map allowed me to replace the disk. It's now resilvering. :) (Still might be nice if ZFS gave a less confusing error message though!)
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby nodarkthings » Tue Jun 01, 2021 1:13 am

Hi! ;)
As you've read in the other thread, I've got no autoimport too and MacOS displays an "unreadable disk" message each time a pool is imported manually, even the ones that have been created with v2.0.1 — that is, perhaps, because I'm using slices, I couldn't try yet with a full disk.
But my pools import correctly, AFAICT.
So your issue seems to be different. :(
nodarkthings
 
Posts: 174
Joined: Mon Jan 26, 2015 10:32 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby Wowfunhappy » Tue Jun 01, 2021 5:08 am

Yeah, can confirm. I woke up this morning to a finished resilver and no more ghost pools, but my pool still doesn't mount after startup until I manually run sudo zpool import Archive in the Terminal.

Would be easy enough to automate with a launchd script, but feels a bit messy. Still wondering if I should just go back to 1.9.2 for reliability...
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby nodarkthings » Tue Jun 01, 2021 5:17 am

The safe procedure would have been to test it on a cloned drive, etc. ;) but now that you've done it, I'd say better stay like that — especially if, as I understand, you've already recreated the pool under v2.0.1.
I don't think there are major issues and hopefully Mr Lundman will keep on building for 10.9 as there's 3 times more downloads for it than for Sierra. 8-) :D
nodarkthings
 
Posts: 174
Joined: Mon Jan 26, 2015 10:32 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby Wowfunhappy » Tue Jun 01, 2021 5:30 am

nodarkthings wrote:The safe procedure would have been to test it on a cloned drive, etc. ;) but now that you've done it, I'd say better stay like that — especially if, as I understand, you've already recreated the pool under v2.0.1.
I don't think there are major issues and hopefully Mr Lundman will keep on building for 10.9 as there's 3 times more downloads for it than for Sierra. 8-) :D


Oh, I have not recreated the pool, I just wiped one of the disks in my mirror and resilvered. I purposefully haven't upgraded the pool yet.

I noticed v2.0.1 doesn't appear to have an uninstall script, however. The old versions had one inside of the DMG...

Edit: I wonder if the import problem is related to viewtopic.php?f=24&t=3511
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Re: There's a ghost ZFS Pool in v2.0.1 on OS X 10.9

Postby nodarkthings » Tue Jun 01, 2021 8:44 am

Wowfunhappy wrote:I purposefully haven't upgraded the pool yet

Good move! ;)
We're not supposed to care about Full Disk access in 10.9, but who knows if it's a side effect... :?
About uninstall, here are the files to remove manually, based on the installer content:
Uninstall ZFS 2.0.1.jpg
Uninstall ZFS 2.0.1.jpg (57.27 KiB) Viewed 6330 times


P.S.: Ah! Ah! I love your new title! :lol:
nodarkthings
 
Posts: 174
Joined: Mon Jan 26, 2015 10:32 am

Re: Adventures with v2.0.1 on OS X 10.9

Postby nodarkthings » Tue Jun 01, 2021 9:46 am

Looking at the Console and in /var/run/disk/ right after boot, InvariantDisks seems to work ok.
Then, I see an impressive number of
Code: Select all
kernel[0]: SPL: set_thread_throughput_named:216: WARNING failed to set thread throughput policy retval: 4  (THREAD_THROUGHPUT_QOS_POLICY fe0002), kmem_move_taskq

ending with
Code: Select all
kernel[0]: SPL: set_thread_latency_named:251: WARNING failed to set thread latency policy retval: 4  (THREAD_LATENCY_QOS_POLICY ff0002), system_delay_taskqSPL: set_thread_throughput_named:216: WARNING failed to set thread throughput policy retval: 4  (THREAD_THROUGHPUT_QOS_POLICY fe0002), system_delay_taskq


Have you got the same?
nodarkthings
 
Posts: 174
Joined: Mon Jan 26, 2015 10:32 am

Re: Adventures with v2.0.1 on OS X 10.9

Postby Wowfunhappy » Tue Jun 01, 2021 11:55 am

nodarkthings wrote:Looking at the Console and in /var/run/disk/ right after boot, InvariantDisks seems to work ok.
Then, I see an impressive number of
Code: Select all
kernel[0]: SPL: set_thread_throughput_named:216: WARNING failed to set thread throughput policy retval: 4  (THREAD_THROUGHPUT_QOS_POLICY fe0002), kmem_move_taskq

ending with
Code: Select all
kernel[0]: SPL: set_thread_latency_named:251: WARNING failed to set thread latency policy retval: 4  (THREAD_LATENCY_QOS_POLICY ff0002), system_delay_taskqSPL: set_thread_throughput_named:216: WARNING failed to set thread throughput policy retval: 4  (THREAD_THROUGHPUT_QOS_POLICY fe0002), system_delay_taskq


Have you got the same?


Yes, they don't stop after boot either. The messages appear in batches, usually-but-not-always exactly once per hour.

nodarkthings wrote:About uninstall, here are the files to remove manually, based on the installer content:
Uninstall ZFS 2.0.1.jpg


Thanks, yeah I saw the list in the package, I just wasn't sure if the installer does anything else (e.g. scripts). I'd rather wait for some official word on proper uninstall procedures, lest I leave my system in an unknown state.
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Re: Adventures with v2.0.1 on OS X 10.9

Postby Wowfunhappy » Wed Jun 02, 2021 5:53 am

@nodarkthings Does Spotlight work on your ZFS pool, on 10.9? It does not on mine since upgrading.
Wowfunhappy
 
Posts: 33
Joined: Sat Jul 21, 2018 11:58 am

Next

Return to Absolute Beginners Section

Who is online

Users browsing this forum: No registered users and 9 guests