Sorry for being slow to chime in on this thread. I live in Boulder, CO and we've had a bit of rain. :-)
Hope all is well your side, everyone safe and sound if may be little wetter than usual.
As Steven pointed out, the warning is benign, but does show that the code I committed to -current is not optimizing the allocation size for L2ARC devices. The fix for this is to find the best place during pool creation/load/import to call vdev_ashift_optimize() on L2ARC devices. I will look into this tomorrow, but feel free to suggest a good spot if you look at it before I can.
The attached patch fixes this for me, not sure if its ideal place for it and consideration may be needed in combination with persistent l2arc. Regards Steve ================================================This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk.
zfs-l2arc-ashift.patch
Description: Binary data
_______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
