FWIW I have not had panics on disk failure. The pool will hang, and often not
recover until a reboot -- depending on the disk failure mode.
I blame sd for this rather than ZFS or FMA, but at the end of the day it is
still suboptimal behavior.
--
bdha
> On Jul 11, 2015, at 16:11, Linda Kateley
+--
| On 2014-12-22 19:34:52, Warren Marts wrote:
|
| KVM virtual machines on illumos each already run in a zone - with a
| specific minimal brand, and qemu-kvm as the zone's primary process. So you
| can apply global zone
+--
| On 2014-03-05 12:29:57, Dan Swartzendruber wrote:
|
| Any explanation as to what was happening?
This is the bug I was hitting: http://smartos.org/bugview/OS-2616
Devices wouldn't be available at boot, but would onc
I've seen that bug on SmartOS. Fixed in the last month or two.
--
bdha
> On Mar 5, 2014, at 11:29, "Dan Swartzendruber" wrote:
>
>
> This is all very strange. I saw stuff like this all the time when I was
> using ZFS on Linux, due to timing where an HBA would not present devices
> quickly en
Further investigation when I wasn't covered in three small children wanting
breakfast definitely suggests this was operator error.
Sorry for the noise.
--
bdha
cyberpunk is dead. long live cyberpunk.
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.
The global zone:
# grep network /etc/zones/icg_mx.xml
igb1:16: flags=1000843 mtu 1500 index 2
inet a.b.c.96 netmask ff00 broadcast 208.72.237.255
Note the lack of a "zone: icg_mx" field in that alias output.
The zone:
# ifconfig -a
lo0:14: flags=2001000849 mtu 8232
index 1
+--
| On 2013-12-08 14:49:43, Lauri Tirkkonen wrote:
|
| entire is always installed matching the gz AFAIK, the -e option
| specifies extra packages to install, and you need omnios-userland. Try
| that.
That sorts it
#
+--
| On 2013-12-08 13:01:35, Lauri Tirkkonen wrote:
|
| I believe this isn't enough, since the zone install only installs
| entire. It would work if entire depended on omnios-userland, but in the
| meantime you could use
+--
| On 2013-12-08 01:54:21, Eric Sproul wrote:
|
| Your 006 install might be missing the omnios-userland incorporation. It
| was left out of the default install by mistake but wasn't apparent until
| the repo had post-0
I have the system pinned to r151006, but this doesn't appear to impact zone
installation.
https://gist.github.com/anonymous/7851777/raw/fdb2745ef15a9b00cdc89383e5b2f3f9bfe71ec7/gistfile1.txt
Is this behavior expected? I'd personally expect that if you install a zone of
a given release of the OS,
JBODs tend to be behind expanders which can cause major headaches. If your
model allows for all in-chassis, its definitely a nicer way to go.
Depends on your use cases and requirements.
Tobias Oetiker wrote:
>Hi Eric,
>
>Today Eric Sproul wrote:
>
>> Tobi,
>> I'd recommend reviewing the parts
+--
| On 2013-10-30 14:29:06, Eric Sproul wrote:
|
| Tobi,
| I'd recommend reviewing the parts lists that Joyent publishes:
| https://github.com/joyent/manufacturing
|
| See the parts_database.ods file. It's mostly Super
12 matches
Mail list logo
