Discussion:
Does zfs-fuse "zpool create" accepts "-o ashift=12" or not?
(too old to reply)
Durval Menezes
2013-08-16 22:00:48 UTC
Permalink
Hi folks,

Using PLD-RCD with Gordan's excellent RPM here to create a pool on a
machine I'm bringing up from a backup; tried to specify ashift=12 on zpool
create but it just barfed:

property 'ashift' is not a valid pool property


Searched the list archives but was not able to find anything definitive,
just a somewhat old message from someone who had the same issue and a reply
from Emmanuel that there was a patch to implement that which was supposed
to have been applied...

So, what's the official position?

Cheers,
--
Durval.
--
--
To post to this group, send email to zfs-fuse-/***@public.gmane.org
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Emmanuel Anne
2013-08-16 22:33:09 UTC
Permalink
... which was supposed to be applied probably but never was apparently.
No idea what this commit was supposed to be anyway, I guess it was not in
the post ?
Anyway my onnv-gate tree is long gone, so no idea, all I can say is that
clearly this commit was never merged, the property does not exist.
Sorry, too old stuff !
Post by Durval Menezes
Hi folks,
Using PLD-RCD with Gordan's excellent RPM here to create a pool on a
machine I'm bringing up from a backup; tried to specify ashift=12 on zpool
property 'ashift' is not a valid pool property
Searched the list archives but was not able to find anything definitive,
just a somewhat old message from someone who had the same issue and a reply
from Emmanuel that there was a patch to implement that which was supposed
to have been applied...
So, what's the official position?
Cheers,
--
Durval.
--
--
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an
For more options, visit https://groups.google.com/groups/opt_out.
--
my zfs-fuse git repository :
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary
--
--
To post to this group, send email to zfs-fuse-/***@public.gmane.org
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Gordan Bobic
2013-08-16 22:45:33 UTC
Permalink
IIRC settable ashift was a ZoL feature. If you can dig out the commit
for it from the ZoL tree, you might find it can be patched into ZF's
zpool implementation reasonably cleanly.

The only other thing I can think of is to use ZoL's zpool to zpool
create initially with the correct ashift.
Post by Emmanuel Anne
... which was supposed to be applied probably but never was apparently.
No idea what this commit was supposed to be anyway, I guess it was not
in the post ?
Anyway my onnv-gate tree is long gone, so no idea, all I can say is that
clearly this commit was never merged, the property does not exist.
Sorry, too old stuff !
Hi folks,
Using PLD-RCD with Gordan's excellent RPM here to create a pool on a
machine I'm bringing up from a backup; tried to specify ashift=12 on
property 'ashift' is not a valid pool property
Searched the list archives but was not able to find anything
definitive, just a somewhat old message from someone who had the
same issue and a reply from Emmanuel that there was a patch to
implement that which was supposed to have been applied...
So, what's the official position?
Cheers,
--
Durval.
--
--
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google
Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it,
For more options, visit https://groups.google.com/groups/opt_out.
--
http://rainemu.swishparty.co.uk/cgi-bin/gitweb.cgi?p=zfs;a=summary
--
--
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send
For more options, visit https://groups.google.com/groups/opt_out.
--
--
To post to this group, send email to zfs-fuse-/***@public.gmane.org
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Emmanuel Anne
2013-08-16 22:48:49 UTC
Permalink
IIRC settable ashift was a ZoL feature. If you can dig out the commit for
it from the ZoL tree, you might find it can be patched into ZF's zpool
implementation reasonably cleanly.
The only other thing I can think of is to use ZoL's zpool to zpool create
initially with the correct ashift.
Yes, from what I vaguely remember it was an internal property of the
pools, but not changeable here. So a pool created with the right value
should work without problem in zfs-fuse, and it's probably the easiest
solution here.
--
--
To post to this group, send email to zfs-fuse-/***@public.gmane.org
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Gordan Bobic
2013-08-16 22:57:32 UTC
Permalink
Post by Gordan Bobic
IIRC settable ashift was a ZoL feature. If you can dig out the
commit for it from the ZoL tree, you might find it can be patched
into ZF's zpool implementation reasonably cleanly.
The only other thing I can think of is to use ZoL's zpool to zpool
create initially with the correct ashift.
Yes, from what I vaguely remember it was an internal property of the
pools, but not changeable here. So a pool created with the right value
should work without problem in zfs-fuse, and it's probably the easiest
solution here.
Yeah. It'd be rather neat, though, to backport the patch from ZoL. But
then again, so would pool v28 support (last compatibility point between
Solaris and other implementations)...

Gordan
--
--
To post to this group, send email to zfs-fuse-/***@public.gmane.org
To visit our Web site, click on http://zfs-fuse.net/
---
You received this message because you are subscribed to the Google Groups "zfs-fuse" group.
To unsubscribe from this group and stop receiving emails from it, send an email to zfs-fuse+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/***@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.
Loading...