I used to get this more often when I had hierarchical filesystems like this.
The problem was, (from memory here, so may be slightly off), that at
some point a replication had behaved (through failure or some other
means) not quite optimally and there was a spare directory created
inside the
Evil tuning here:
https://www.solaris-cookbook.eu/solaris/solaris-10-zfs-evil-tuning-guide/
It's at the bottom. Where it says "Disabling the ZIL (Don't)"
I could see a lack of TRIM/erase support in background as a strong
possibility caused by continuous use of blocks from the L2ARC over time.
Out of curiosity, if you disable the zil through the evil zfs tuning
wiki mechanisms (diagnostic purposes only), does it dramatically help?
If not, there's something else going on, if yes, it could be that the
l2arc and zil are interfering with each other (I could imagine that the
l2arc is
NFS writes (especially for lots of small files) to omniOS *really*
benefit from having ZIL on those SSD.
You could remove the cache from the pool, carve of an 8GB chunk for ZIL
on each and the rest for L2arc if you want that.
then add a mirrored zil using the 8GB chunks and the other
wouldn't it be easier to use your local MTA (postfix, sendmail) to do this?
Then SMF just has to execute /bin/mail or equivalent and your MTA can act as an
outbound relay agent.
Sent from my android device.
-Original Message-
From: Johan Kragsterman
To:
Not myself, yet, but I have the same setup, coincidentally or not, and
would be interested in the answer as well.
On 7/20/2017 9:53 PM, Dan McDonald wrote:
> I have an OmniOS r151022 box. (You may have heard me talk about it from time
> to time. :) ) Some of its zones use other publishers for
Tobi, this is a great idea but let me request minor clarification. Is
that the amount of money that you'd be willing to pay annually for
update service, or actual amount paid previously, or something else?
It may be worth having 2 columns, 1 for update services and 1 for support?
I can see
There are quite a bit of things to look at.
One question: do you have deduplication turned on?
I have seen things like this (with or without dedup) as a result of
memory exhaustion. I happen to know that the x4540 can only hold about
32GB of ram, so this seems like a possibility.
you might want
Kvm/libvirt
it goes a good ways, but then cycles back. I set it to verbose and kmdb
and am at the kmdb prompt with the following traceback:
I set console=ttya, acpi = off, single user = on, verbose = on, and kmdb
= on and selected option 1 to go into single user mode.
Aside: it'd be nice
On 3/2/2017 9:18 AM, Dan McDonald wrote:
On Mar 2, 2017, at 2:29 AM, Stephan Budach <stephan.bud...@jvm.de> wrote:
Next is some kind of stack trace and finally
BTX halted
Is that Xen-based?
Dan
Yes, it is.
Doug Hughes just showed me the same thing, and I'm pretty sure he's Xen t
On 2/28/2017 10:27 PM, Dan McDonald wrote:
On Feb 28, 2017, at 9:33 PM, Doug Hughes <d...@will.to> wrote:
I get an endless boot loop.
libvirt/kvm on Centos7
It took me a while, but I managed to get a screenshot, which was very difficult
and took about 15 tries.
You can use the BSD
I could try it on libvirt/qemu.
On Feb 28, 2017 3:14 AM, "Stephan Budach" wrote:
> Hi Dan,
>
> would that allow me to run OmniOS on a Xen-based Oracle VM? Frankly, I
> didn't manage to get that one up due to restrained resources on my end -
> and it since hasn't been
On 2/22/2017 12:32 PM, Peter Tribble wrote:
On Wed, Feb 22, 2017 at 5:23 PM, Doug Hughes <d...@will.to
<mailto:d...@will.to>> wrote:
no luck:
# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh
--reject pkg:/network/ssh/ssh-key --reject
pkg:/ser
On 2/22/2017 12:26 PM, Dan McDonald wrote:
On Feb 22, 2017, at 12:23 PM, Doug Hughes <d...@will.to> wrote:
no luck:
# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject
pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh pkg:/network/openssh
pkg:/network/o
no luck:
# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject
pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh
pkg:/network/openssh pkg:/network/openssh-server
Creating Plan (Solver setup): /
pkg install: No matching version of network/openssh can be installed:
Sorry for including the previous thread in there. mea culpa.
On 2/22/2017 11:55 AM, Doug Hughes wrote:
I'm very delayed in this but had an opportunity to tackle the ugprade.
Unfortunately the prerequesite stage of upgrade to openssh is failing:
# /usr/bin/pkg install --no-backup-be --reject
I'm very delayed in this but had an opportunity to tackle the ugprade.
Unfortunately the prerequesite stage of upgrade to openssh is failing:
# /usr/bin/pkg install --no-backup-be --reject pkg:/network/ssh --reject
pkg:/network/ssh/ssh-key --reject pkg:/service/network/ssh --reject
When I had it in production, I used SolarFlare for 10g (but not 40). I'm
contributing this in case it helps..SolarFlare open sourced the code and
contributed it and there have been a couple of posts to this list in the
past with the updated stuff. (I contributed some fixes for add_drv). It
I have not tried dlna or fish shell, but the rest are either integrated or
just a package install away. I have a web server with Marian, NFS, and
samba where I store axis camera videos. The one that took the most fiddling
was samba because the integrated samba is a bit different than standard
I've used the Intel 520DA2, but not the 550 specifically. Works well.
Not sure if that is useful information or not.
On 6/8/2016 12:55 PM, Dale Ghent wrote:
Hello,
I'm interested in knowing if any users of OmniOS have hardware that is equipped
with a Intel X550 10Gb ethernet chip *with* SFP
I didn't see this show up on the list, so I'm trying again.
Been seeing this a bit lately on a server with 96GB ram where the zil is
limited to 48GB. Under heavy NFS load (caused by user running parallel
find/xargs/rm clean job), it sends the machine into desparation memory
and causes
Been seeing this a bit lately on a server with 96GB ram where the zil is
limited to 48GB. Under heavy NFS load (caused by user running parallel
find/xargs/rm clean job), it sends the machine into desparation memory
and causes it to be unreachable for a while. (the server is 24 x SSD,
and I/O
Interesting issue with flow control that I can't prove but suspect is ixgbe
driver related. I wonder if anybody has seen this. The switch is Dell
Force10 S4810. I have enabled bidirectional flow control on the port.
(standard broadcomm chipset).
If I turn on rx flow control in the driver by
(this is a new thing. I've updated a bunch of other machines last week)
root@xyr-3-3-1:/root# /usr/bin/pkg unset-publisher omnios
icy=require-signatures -g http://pkg.omniti.com/omnios/r151016/
omniosature-pol
1-0.151016-3-1:/rot# /usr/bin/pkg update --be-name=omnios-r151016
entire@11,5.1
DOH.. I tried this multiple times and didn't notice the clear symptoms
of paste error... (pasting from 'more' -- baaddd)
thanks for the clue-by-4. all good.
On 1/6/2016 6:29 PM, Dan McDonald wrote:
On Jan 6, 2016, at 4:54 PM, Doug Hughes <d...@will.to> wrote:
File &qu
had a local IPS server.. it went SNAFU. totally lost..
Has anybody recovered an IPS from the local installed packages that came
from that repo to generate a new one?
/var/pkg/publisher//pkg/...
it looks like the complete catalog is in there that could be used
rebuild a repo.
Ideas?
I like the Samsung 850 line. It has been around and quite stable for some
time. We haven't had any problems with device availability. (depending on
how much writing you are doing, you'd probably best avoid the EVO and stick
with straight 850 or 850 pro)
On Wed, Dec 9, 2015 at 12:35 PM, Tobias
You can look at /etc/release. It's on the 1st line.
Sent from my android device.
-Original Message-
From: Chris Siebenmann
To: omnios-discuss@lists.omniti.com
Sent: Wed, 02 Dec 2015 14:30
Subject: [OmniOS-discuss] What's the best way to detect OmniOS version,
size? It's not
like vendors don't change specs on newer versions of the same model sometimes
:(. What exactly is it? Is it by any chance one of those 4K drives with a
jumper that controls whether or not it lies about the physical sector size?
On Nov 20, 2015, at 8:44 PM, Doug Hughes <d...@will
All 1gig interfaces are auto-mdix these days, which means they will
auto-negotiate and no special crossover cable is needed for host-to-host.
You can use ipadm to set the mtu like so:
ipadm set-ifprop -p mtu=9000 -m ipv4 bnx0
If the mtu updated in the driver.conf file is needed, you'll need to
Probably something for Illumos, but you guys may have seen this or may like
to know.
I've got a 10g connected Xyratex box running OmniOS, and I noticed that no
matter how many streams (1, 2, 3) I only get 100MB/sec write throughput and
it just tops out. Even with 1 stream. This is with the
)
On 8/23/2015 6:20 AM, Alexander Lesle wrote:
Hello Doug Hughes and List,
I use the same HGST drive and they have all 4 TB capacity in my pools.
,-[ ]-
|
| AVAILABLE DISK SELECTIONS:
|0. c2t0d0 VMware-Virtualdisk-1.0 cyl 5012 alt 2 hd 224 sec 56
| /pci@0,0/pci15ad
, Alexander Lesle wrote:
Hello Doug Hughes and List,
I use the same HGST drive and they have all 4 TB capacity in my pools.
,-[ ]-
|
| AVAILABLE DISK SELECTIONS:
|0. c2t0d0 VMware-Virtualdisk-1.0 cyl 5012 alt 2 hd 224 sec 56
| /pci@0,0/pci15ad,1976@10/sd@0,0
|1. c2t1d0
Gunther, are you using vmware esx as an NFS client to OmniOS or are using
OmniOS as an NFS client to ESX?
On Tue, Aug 11, 2015 at 11:28 AM, Günther Alka a...@hfg-gmuend.de wrote:
In my own setups, I use OmniOS 151014 (initial release) with NFS to ESXi
5.5U2 which is very stable with vmxnet3
thinking for a
while to use as a ZIL+L2ARC.
Could you share with us your experiences? I would be interested in server
usage. Thanks.
2015.07.15. 22:42 keltezéssel, Doug Hughes írta:
We have been preferring commodity SSD like Intel 320 (older), intel 710,
or currently, Samsung 850 pro. We
We have been preferring commodity SSD like Intel 320 (older), intel 710, or
currently, Samsung 850 pro. We also use it as boot drive and reserve an 8GB
slide for ZIL so that massive synchronous NFS IOPS are manageable.
Sent from my android device.
-Original Message-
From: Matthew Lagoe
For things that require that, we've just been going with dual-head
controller boxes.
One such example is Seagate (nee Xyratex) which has a dual head box and
then you can use something like pacemaker to fail over by force pool
import/export. You might need to combine this with something like
It wasn't entirely clear from the video.. is this enabled automatically, or
must an /etc/system variable be set to take advantage of it?
(We're probably not target customer since our zpools are setup once and
done; no incremental growth/change, except very infrequently upgrade disks
in place with
The equivalent TCP raw tunings for Solaris based OS's
ndd -set /dev/tcp tcp_xmit_hiwat 1048576
ndd -set /dev/tcp tcp_recv_hiwat 1048576
ndd -set /dev/tcp tcp_max_buf 4194304
Those are the raw tunables and if you run get on those you'll see that they
are different than what's in ipadm. One is
, at 2:41 PM, Doug Hughes d...@will.to wrote:
ndd -set /dev/tcp tcp_xmit_hiwat 1048576
ndd -set /dev/tcp tcp_recv_hiwat 1048576
ndd -set /dev/tcp tcp_max_buf 4194304
Umm... not as much now. The ipadm(1M) Michael showed is the moral
equivalent, and better supported.
Dan
I can confirm that no more nlockmgr's for us since going with r14!
On Thu, May 7, 2015 at 3:26 PM, John Barfield john.barfi...@bissinc.com
wrote:
Okay awesome! I’ve been holding back on upgrading but now I probably will.
John Barfield / Sr Principal Engineer
+1 (214) 425-0783/
this is a relatively fresh install and not much going on on the machine,
and I see somehow that the pkg repo got corrupted relatively recently on r14
t@x4275-3-15-20:/usr/local/orca-r535# pkg refresh
An error was encountered while attempting to read image state information
to perform the
Didn't work. still 0. I ended up copying the repo from another machine
built at the same time and then doing a refresh.
On 5/6/2015 11:00 PM, Dan McDonald wrote:
pkgrepo rebuild -s repo-path
Dan
Sent from my iPhone (typos, autocorrect, and all)
On May 6, 2015, at 9:53 PM, Doug Hughes d
I managed to get my system in a state with dd test across a bunch of
client nodes (4k writes, many nodes in parallel, all to the same file -- by
mistake, I meant to do many files), that all of the ttys except for
/dev/console are stuck. It was showing signs of desparation swapping a few
times, but
Yes, absolutely. We've run into this same problem, exactly as you
describe, in Solaris10 (all versions)
You can catch it with a kernel dump, but you have to be wary and quick.
keep a vmstat 3 open (or similar), and when free mem drops below 5GB or
so, be ready. As soon you start seeing PO or
Good catch! I take if you've run into this before. Luckily, I also admin
the firewall so I added an exception for the outbound threat trigger.
On 5/1/2015 5:55 PM, John D Groenveld wrote:
In message CAOpmc6xZ9ViDe1YnWTjOy=+VT-wiuHJYwuRgvxrfKLp+==g...@mail.gmail.com
, Doug Hughes writes
haven't had time to upgrade all my kayak stuff to r151014 yet, so going to
r151012 and then doing the pkg upgrade with alt BE, but running into a
consistent problem
After the install and making sure I have all of the latest r151012 there, I
do the unset publisher, the set publisher, and then
I've seen something similar to this in Solaris10 (that Oracle won't fix).
It was diganosed as basically 'storage is too slow to service requests.
Throw more hardware at it.. What happens is that nfs buffers just keep
building up and building up (even if it's a read request storm) and the I/O
...@omniti.com wrote:
On Apr 24, 2015, at 12:24 AM, Doug Hughes d...@will.to wrote:
Aye, fixed in r151014. Somewhere during the fmd storm and reboots, I
guess they all just disappeared.
Don't suppose you have an upstream open source version of scanpci to
include? (it's a pretty useful
it shows in lspci and is brand new. I'm pretty sure it still works. Most
likely it's the optics that is causing this. (it also shows in POST)
On Thu, Apr 23, 2015 at 10:36 AM, Tim Rice t...@multitalents.net wrote:
On Wed, 22 Apr 2015, Doug Hughes wrote:
Even if it doesn't recognize the SFP
, but it
still fails to attach even though lspci sees the card just fine and it
shows up in PROM.
On Thu, Apr 23, 2015 at 11:03 AM, Doug Hughes d...@will.to wrote:
it shows in lspci and is brand new. I'm pretty sure it still works. Most
likely it's the optics that is causing this. (it also shows in POST
I'll try a reboot into r151012 tonight.
On Thu, Apr 23, 2015 at 4:07 PM, Dan McDonald dan...@omniti.com wrote:
On Apr 23, 2015, at 3:58 PM, Doug Hughes d...@will.to wrote:
Oddly, removing the SFP modules makes no difference. Replacing the
modules - still doesn't show up. I really do
Ethernet up 1 full ixgbe1
root@x4275-3-15-39:/root#
back in business.
On 4/23/2015 4:07 PM, Dan McDonald wrote:
On Apr 23, 2015, at 3:58 PM, Doug Hughes d...@will.to wrote:
Oddly, removing the SFP modules makes no difference. Replacing the modules -
still doesn't
it seems like an odd omission. But I can't find the man page for cpp
anywhere.
I tried find in /usr/share/man to see if it was anywhere else, but couldn't
find it. It's not that I don't have man pages installed. There are lots,
but cpp is notably missing.
I'm going to start with replacing the SFP+ modules as soon as they
arrive and go from there. There's a fair chance that might just take
care of it. The odd thing is, though, that the ones that are in there
were accepted previously. Head scratcher, I know.
On 4/22/2015 7:25 PM, Dan McDonald
On 4/22/2015 7:52 PM, Dan McDonald wrote:
- Addition of netperf (2.6.0) and iperf (3.0.11) as native OmniOS
packages. They are both 64-bit binaries, but that shouldn't be a problem.
They are also stock for now, but I reserve the right to add features
(command-line IPsec comes to
recognize the SFP+ any more (though it was running fine
for weeks on r151012), I wouldn't expect it to not see the card at all. (It
shows in lspci, but not in dladm)
On Wed, Apr 22, 2015 at 5:36 PM, Dan McDonald dan...@omniti.com wrote:
On Apr 22, 2015, at 5:22 PM, Doug Hughes d...@will.to
I'm interested in this too! Once upon a time we used Orcallator for this on
Sol10, which is quite a bit like Ganglia, but uses the venerable SEtoolkit
to pull stats. I'd be curious what other people are doing here since all of
that stuff is pretty much unmaintained for a decade, though it provided
My take to summarize the two choices:
1) use a NGZ in its on pool and you have complete isolation and you can
move it from machine to machine as needed. More setup required, but doable.
2) use a pre-packaged apache or nginx that installs all of the read-only
stuff in your regular root pool (this
We have a couple of machines with all SSD pool (~6-10 Samsung 850 pro is
the current favorite). They work great for IOPS. Here's my take.
1) you don't need a dedicated zil. Just let the zpool intersperse it
amongst the existing zpool devices. They are plenty fast enough.
2) you don't need an
Does anybody know if anybody is planning on updating the list of free
packages in a repo somewhere? in r12 using the public omniti repo (r10) was
a bit tenuous. I imagine it will be even mor so with r14. it'd be nice to
reference an up to date open source repo somewhere for things like postfix,
On 3/29/2015 9:51 AM, Matthew Lagoe wrote:
The intel cards are nice but they don't have any cx4 cards so we don't use
them. Copper connections have less latency on short links then fiber as you
don't have the electric to optical conversion (when done properly)
Do yourself a huge favor and go
any recommendations? We're having some pretty big problems with the Solarflare
card and driver dropping network under high load. We eliminated LACP as a
culprit, and the switch.
Intel? Chelsio? other?
- Doug___
OmniOS-discuss mailing list
and the Supermicro equivalents are rock solid. The
X540 probably is too, I just haven't used it. I prefer the Supermicro
branded Intel cards because the firmware is not as picky about the twin-ax
cables used.
-Chip
On Thu, Mar 26, 2015 at 11:24 AM, Doug Hughes d...@will.to wrote:
any
I'm having an issue with r*12 with 10g Solarflare interfaces setup in an
aggregate simultaneously dropping for a while for no apparent reason and
then coming back. Oddly, I can see them leaving the port channel and
dropping on the switch side, but there's no log messages or anything on the
client
Agh! ick. please don't use LD_LIBRARY_PATH. If at all possible, rebuild
your binary with -R /opt/pgsql/lib passed to the linker
(when combined with NFS, LD_LIBRARY_PATH can lead to all sorts of evil
behaviors, when combined with NFS and 64/32 bit, multiply by 2!)
/peave
On 1/26/2015 6:02
the machine has been up for a while. It seems like something funky is going
on in the network stack. it pings ok.. ssh inbound new sessions no longer
work. The master ssh process isn't bound to port 22 any more (pfiles).
Active ssh session to this machine continues to work, however.
Also, pkg
this suddenly started causing a
problem!
I'm glad it turned out to be something simple.
On Thu, Dec 18, 2014 at 1:21 PM, Dan McDonald dan...@omniti.com wrote:
On Dec 18, 2014, at 11:26 AM, Doug Hughes d...@will.to wrote:
Here's the simplest test... I start up ttcp -r on the server, it binds
I have a strange console message on a relatively newly installed machine:
root@x4275-3-15-39:/root# uname -a
SunOS x4275-3-15-39 5.11 omnios-f808c81 i86pc i386 i86pc
root@x4275-3-15-39:/root# more /etc/release
OmniOS v11 r151012
Copyright 2014 OmniTI Computer Consulting, Inc. All rights
I'm seeing these on a 'mature' x4275 server. I tried googling this, but
didn't turn up anything. Any idea what it means or how severe it is?
###!!! [Child][DispatchInterruptMessage] Error: Unknown message: not
processed
###!!!
Solarflare cards setup in LACP to the switch stack.
I'd say this is ok to release/bundle!
(I'd be happy to volunteer a sfxge.conf for this, also we should use the
Solaris postinstall or a variant of it to do the correct add-drv and
driver_aliases stuff.)
On Thu, Sep 25, 2014 at 3:16 PM, Doug Hughes d
On 9/19/2014 9:03 PM, Saso Kiselkov wrote:
On 9/20/14, 1:23 AM, Mark wrote:
On 20/09/2014 5:13 a.m., Dan McDonald wrote:
On Sep 19, 2014, at 11:44 AM, Doug Hughes d...@will.to wrote:
Is anybody using Solarflare 10G cards with OmniOS. I have a 2010
vintage of Openindiana (yeah, I should
I got the miniroot (earlier emails) worked out by getting the bloody
build and building a new miniroot, but I suspect that this is making the
final boot non-functional because it's not backwards compatible because
it includes new com.delphix:embedded_data.
The kayak install works fine, but I
On 9/22/2014 10:19 PM, Dan McDonald wrote:
On Sep 22, 2014, at 9:27 PM, Doug Hughes d...@will.to wrote:
I got the miniroot (earlier emails) worked out by getting the bloody build and
building a new miniroot, but I suspect that this is making the final boot
non-functional because it's
On 9/19/2014 9:03 PM, Saso Kiselkov wrote:
Ok, got it to build cleanly, code at:
https://github.com/skiselkov/illumos-gate/tree/sfxge
Unique commits in that branch:
1c3fe595 - initial commit of the sfxge pretty much as-is from the webrev
(plus a few formatting fixes to get git to
I had some problems with 006 also, but these appear to be different so
far. I took an omniOS 008 machine and upgraded to 010 using the standard
upgrade mechanism. Totally successul. My /etc/release is updated and
everything is fine. Then I made sure that the kayak and kayak-server
packages
On 9/15/2014 4:00 PM, Dan McDonald wrote:
On Sep 15, 2014, at 3:26 PM, Doug Hughes d...@will.to wrote:
I had some problems with 006 also, but these appear to be different so far. I
took an omniOS 008 machine and upgraded to 010 using the standard upgrade
mechanism. Totally successul. My
On 5/29/2014 11:19 AM, Dan Swartzendruber wrote:
On 5/28/2014 10:34 AM, Saso Kiselkov wrote:
On 5/28/14, 4:08 PM, Schweiss, Chip wrote:
Intel has several SATA SSDs with proper super-cap protected caches that
make good log devices.
I'd recommend looking at a Intel DC S3700. The 200 GB or 400
On 5/28/2014 10:34 AM, Saso Kiselkov wrote:
On 5/28/14, 4:08 PM, Schweiss, Chip wrote:
Intel has several SATA SSDs with proper super-cap protected caches that
make good log devices.
I'd recommend looking at a Intel DC S3700. The 200 GB or 400 GB
varieties promise ~3 4k random write IOPS
Any documentation on getting a CIFS share working with OmniOS? All I'm
finding on the web is Solaris11, which has some key things that OmniOS
doesn't in smbadm, so the instructions fall apart rather early.
(Tried this also, but many stale links:
On 5/7/2014 10:57 PM, Dan Swartzendruber wrote:
Any documentation on getting a CIFS share working with OmniOS? All I'm
finding on the web is Solaris11, which has some key things that OmniOS
doesn't in smbadm, so the instructions fall apart rather early.
OpenIndiana instructions?
None that
On 5/7/2014 11:00 PM, Dan Swartzendruber wrote:
On 5/7/2014 10:57 PM, Dan Swartzendruber wrote:
Any documentation on getting a CIFS share working with OmniOS? All I'm
finding on the web is Solaris11, which has some key things that OmniOS
doesn't in smbadm, so the instructions fall apart rather
Yes, it is missing a few key libraries, I reported that in a similar email back
around december but it seems to have gone unfixed in the interim. If you find
my posts, it indicates the things that I found and fixed. Luckily, it is easy
to uncompress, mount and fix the miniroot with the missing
Thanls, Eric!
Sent from my android device.
-Original Message-
From: Eric Sproul espr...@omniti.com
To: Doug Hughes d...@will.to
Cc: omnios-discuss@lists.omniti.com omnios-discuss@lists.omniti.com, Randy
S sim@live.nl
Sent: Thu, 13 Mar 2014 10:16 AM
Subject: Re: [OmniOS-discuss
On 2/27/2014 10:56 AM, Dan Swartzendruber wrote:
If you have the pool on the raw device (i.e. you haven't created any
slices/partitions and instructed zfs to use the whole 'disk'), and the
device suddenly appears to the OS with a larger size, then ZFS will use
all the space available. This also
On 2/18/2014 10:54 PM, Marion Hakanson wrote:
Thanks for everybody's comments. More data from folks doing similar stuff
is always welcome.
Marion Hakanson wrote:
Out of curiosity, what HBA is being used for these drives (and slog)
in this R720xd, H710 or H310? Something else?
Derek
On 2/3/2014 10:12 AM, Dan Swartzendruber wrote:
Hello,
I have a few questions about a project that i am trying to work on,
needless to say i have 1 80GB SSD Drive that i can fit in this case, the
rest of the drives are a RaidZ2 configuration and there cannot be anymore
added Disks to this
On 2/3/2014 10:53 AM, Matthew Mabis wrote:
This is perfect, I was reading on Hardforum from a user named GEA saying that
its unsupported and not recommended about a year ago so i figured why not bring
the question to the forum and get the answer to Why!
This information will get things
regarding the possibility of multi-processor shifting and counters, it
seems like that would be fairly easy to rule out (however unlikely) by
running pbind on the iostat process to keep it pegged to a specific core.
On Fri, Dec 13, 2013 at 10:38 AM, Richard Elling
This may be AMD64 specific. I haven't checked in depth, but the following
missing libraries (from miniroot.gz) prevent a successful pxe installation.
Most of them are related to zfs either in creating the filesystem or in the
implicit execution of share at the end of creating rootfs. In most cases
I'm trying to do a kayak install and running into some problems. I've
gotten as far as tftp loading the base miniroot, but when it comes time
to curl down the release bundle for install, the amd64 curl is missing
libidn and some other things.
(I also tried with bloody, but that failed to
91 matches
Mail list logo