gmzang / maczfs

Automatically exported from code.google.com/p/maczfs
Other
0 stars 0 forks source link

Plugging in ZFS pool shows dialog 'ZFS is not supported' #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
When plugging in a ZFS pool, the automounter displays 'ZFS is not supported'

Original issue reported on code.google.com by alex.ble...@gmail.com on 24 Oct 2009 at 9:16

GoogleCodeExporter commented 8 years ago

Original comment by alex.ble...@gmail.com on 24 Oct 2009 at 9:28

GoogleCodeExporter commented 8 years ago
This definitely occurs on Snow Leopard Server with the 10A286 bits. I assume it 
also occurs on non-Server, but 
have not tested it.

Original comment by dmz...@gmail.com on 24 Oct 2009 at 10:22

GoogleCodeExporter commented 8 years ago
Thanks for the confirmation. 

The source (or binaries, for that matter...) were never relased for the 10a286 
bits. Does it occur on the 119 
bits?

http://groups.google.com/group/zfs-macos/browse_thread/thread/2074254161f4fa49

Original comment by alex.ble...@gmail.com on 24 Oct 2009 at 10:25

GoogleCodeExporter commented 8 years ago
I think it happens on Snow Leopard when the partition type is set to ZFS. I 
created a
pool on a "Free Space" partition and it doesn't display that message anymore.

Using zfs-119_src on 10.6.1.

Original comment by caio...@gmail.com on 24 Oct 2009 at 2:52

GoogleCodeExporter commented 8 years ago
This issue is referring to this dialog box correct?

If so, this same dialog box will appear even if all ZFS files (zfs, zpool, 
libzfs.dylib, zfs.fs, and zfs.kext) are 
removed from the system. The same dialog box occurs with src[1] build when the 
drive is formatted ZFS[2].

OS:     10.6.1 (10B504)
Arch:  x86_64

[1] 
http://github.com/dustin/mac-zfs/tree/15cf8709a3e3fd0baef9f2cd920a1cd928a50de2
[2] diskutil partitiondisk /dev/disk2 GPTFormat ZFS %noformat% 100%

Original comment by jason.richard.mcneil on 24 Oct 2009 at 7:18

Attachments:

GoogleCodeExporter commented 8 years ago
Jason, I confirm that is the exact situation I'm describing.

If you don't do [2], you get the standard dialog that offers to initialize the 
disk,
though the zpool is fine in either case.

Original comment by dsalli...@gmail.com on 24 Oct 2009 at 10:31

GoogleCodeExporter commented 8 years ago

Original comment by dsalli...@gmail.com on 24 Oct 2009 at 10:32

GoogleCodeExporter commented 8 years ago
I've resolved this locally.  Will try to get it into the installer soon.

Original comment by dsalli...@gmail.com on 25 Oct 2009 at 3:49

GoogleCodeExporter commented 8 years ago
Issue 12 has been merged into this issue.

Original comment by dsalli...@gmail.com on 25 Oct 2009 at 3:50

GoogleCodeExporter commented 8 years ago
Glad to hear I was wrong about it being a separate issue. Looking forward to 
the first real bug fix of the project.

Original comment by jason.richard.mcneil on 25 Oct 2009 at 4:23

GoogleCodeExporter commented 8 years ago
I just pushed up the code.  Uploading a package to github and the list.

Original comment by dsalli...@gmail.com on 25 Oct 2009 at 6:01