vfs.zfs.write_to_degraded missing in 10.1?

[Lacey Powers]

Hello Gabor,

It looks like this was an upstream behavior that was changed.

Here's the bug from Illumos:

https://www.illumos.org/issues/4976

And it was pulled in in r269010in FreeBSD

https://svnweb.freebsd.org/base?view=revision&revision=269010

I'm not entirely sure about what the changes mean, but it seems like it 
will always try for the behavior of the vfs.zfs.write_to_degraded 
sysctl, except in instances where the vdev is non-redundant and 
top-level.It might help to ask for further clarification on an Illumos 
or OpenZFS mailing list, or in the IRC channels on freenode for each, 
#illumos or #openzfs.

Hope that helps. =)

Regards,

Lacey


On 04/29/2015 14:40, Gabor Radnai wrote:
> Hi,
>
> I run 10.1-stable (r281854), is it possible I missed the announcement of
> removing vfs.zfs.write_to_degraded sysctl variable?
>
> The Handbook's Advanced Topics 20.6 is mentioning this variable as "to
> allow writing to degraded vdevs to prevent the amount of free space across
> the vdevs from becoming unbalanced, which will reduce read and write
> performance."
>
> How can this be achieved currently?
>
> Thanks.
> _______________________________________________
> freebsd-fs at freebsd.org  mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to"freebsd-fs-unsubscribe at freebsd.org"