-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZFS pool on Core Storage, created with a 20130712 build of zfs-osx, can not be used by ZEVO #41
Comments
I can see a couple of things that are suspect here;
If we create a pool version 28, then it should not set the feature-flags. They belong only to pool version 5000.
That is clearly undesirable. |
In the ZEVO support forum: Alignment at the Core Storage LVM layer, ashift above?
|
Without Core Storage –
– and:
None of those things are an obstacle to ZEVO Community Edition 1.1.1:
|
Terminal output below. ZEVO on Mountain Lion.
|
In response to suggestions from ilovezfs
zpool import -d /dev
With force
Slice 2, symbolic linking
|
I experimented with setting the ashift value to 9 at time of creation by MacZFS prototype. The setting did not work around the issue. |
In the ZEVO support forum: Getting ashift property values: use zdb, not zpool
|
With a 20130712 build of zfs-osx
Preparation
Destruction of a previous test pool
Creation of a version 28 pool
A later review of properties, and an export
With ZEVO Community Edition 1.1.1 on Mountain Lion
Unlocking the Core Storage logical volume:
The issue
Comparison
For a Core Storage logical volume with which there's no difficulty
The text was updated successfully, but these errors were encountered: