Sorry in my haste I posted fred not fred5
See corrections below :-)
Richard Skelton wrote:
> Hi,
> I have a Sun X4170 with igb network.
> I am using omnios-r151018-ae3141d
> Here are my steps to create a zone called fred5 :-
> dladm show-phys
> LINK MEDIASTATE SPEED
I took a look at your dumps.
Both vmdump.0 and vmdump1 have the same stack:
vpanic()
0xfba90de8()
zfs_acl_ids_create+0x4d2(ff0799931ab0, 2, ff00194bdcb0, ff055d97ddb0
, 0, ff00194bdbf0)
zfs_make_xattrdir+0x96(ff0799931ab0, ff00194bdcb0, ff00194be018,
vNICS MUST end in a number. That's a requirement. "fred0" or "fred23" is
fine, but "fred" breaks things.
Dan
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Hi,
I have a Sun X4170 with igb network.
I am using omnios-r151018-ae3141d
Here are my steps to create a zone called fred :-
dladm show-phys
LINK MEDIASTATE SPEED DUPLEXDEVICE
usbecm0 Ethernet down 10 full usbecm0
igb2
> On Sep 12, 2016, at 5:41 AM, [BLOOM] Piotr Kaminski wrote:
>
> Now, on completely different system - it is new install of OmniOS 151018
> VM under ESXi 6, with passthrough LSI card, the system was solid while
> serving NFS shares. And then I turned on some CIFS shares, one of
Hi everybody
I've just subscribed to the list, although I have been using OmniOS for
a a few years.
I would like go back to the issue raised by Floris van Essen.
Some time ago I had the same issue. I upgraded Omnios from 151014 to
151016 and had the same issue - the host rebooted when accessed