I'll throw my $.02 behind you Jim. Perhaps splitting an SSD is not the
best way to get the most performance out of the SSD.
But even a part of an SSD is a huge win. In fact, separate logs have
always been a win, even back in the pre-ZFS days. I
recall some old Bonnie results from the late '90
. I'll probably keep
them for transaction pools.
For data repos, I'll just have one.
Cheers!
-sam
On Fri, Jan 19, 2018 at 10:49 AM, Sam Nicholson <sam...@ogt11.com> wrote:
> I'll throw my $.02 behind you Jim. Perhaps splitting an SSD is not the
> best way to get the most per
Greetings,
I have read the wiki.
My q is: I'd like to have the root zone be on one network (inside) the
admin network tag, and
then the other physical nic is tagged with, say, prod. And I'd like all
the vms to be there.
So, I have the following:
sandbender is the vm, and sandbooter is the GZ
Interesting. Issue 727 seems to be what I initially thought you had here.
(See Intel errata: SKZ7/SKW144/SKL150/SKX150/SKZ7/KBL095/KBW095 )
I suppose your BIOS might surface the problem differently. (I.e, you
disable XHCI, others disable Hyperthreading.)
For what it's worth, we're seeing
Thanks.
On Wed, Jul 11, 2018 at 1:46 PM, Dan McDonald wrote:
>
>
> > On Jul 11, 2018, at 1:14 PM, Sam Nicholson wrote:
> >
> > What's the (an) accepted way of making an ipv6-to-4 tunnel persist
> across reboots?
> > This config works for me:
> >
> &
What's the (an) accepted way of making an ipv6-to-4 tunnel persist across
reboots?
This config works for me:
ifconfig ip.tun0 inet6 plumb
ifconfig ip.tun0 inet6 tsrc ${myIPV4) tdst ${remoteIPV4) up
ifconfig ip.tun0 inet6 addif $(myIPV6) ${remoteIPV6) up
route add -inet6 default ${remoteIPV6)
