On Fri, Jul 2, 2010 at 9:55 PM, James C. McPherson <j...@opensolaris.org>wrote:
> On 3/07/10 12:25 PM, Richard Elling wrote: > >> On Jul 2, 2010, at 6:48 PM, Tim Cook wrote: >> >>> Given that the most basic of functionality was broken in Nexenta, and not >>> Opensolaris, and I couldn't get a single response, I have a hard time >>> recommending ANYONE go to Nexenta. It's great they're employing you now, >>> but the community edition has an extremely long way to go before it comes >>> close to touching the community that still hangs around here, despite >>> Oracle's lack of care and feeding. >>> >>> http://www.nexenta.org/boards/1/topics/211 >>> >> >> I can't test that, due to lack of equivalent hardware, but did you file a >> bug? >> The dladm code and nge drivers come from upstream, so look for an >> equivalent >> opensolaris bug, perhaps something like >> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6913874 >> -- richard >> >> > > Hi Tim, > does this CR match what you were experiencing? > > http://bugs.opensolaris.org/view_bug.do?bug_id=6901419 > 6901419 dladm create-aggr -u incorrectly rejects some valid ethernet > addresses > > If so - fixed in snv_136. > > The only other dladm CR I can see in the push logs for builds > post 134 is > > 6932656 "dladm set-linkprop -p cpus" can't take more than 32 CPUs > fixed in 138. > > > hth, > James > -- > Senior Software Engineer, Solaris > Oracle > http://www.jmcp.homeunix.com/blog Hi james, Nope. I'm not sure what exactly I was hitting. I've never run into a problem on any release of Opensolaris. I believe I've tested on 126, 132, 133, and 134 (as well as many iterations of older versions). The dladm issue was exclusively on nexenta. --Tim
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss