On Mar 25, 2015, at 11:51 AM, wuffers m...@wuffers.net wrote:
Going to do this as soon as I can.
Solaris docs say to put the following line in etc/system and reboot:
set kmem_flags=0xf
That's correct.
Can't I just set this dynamically like so (so I can potentially skip 2
reboots)?
On Tue, Mar 24, 2015 at 7:44 PM, Dan McDonald dan...@omniti.com wrote:
On Mar 24, 2015, at 7:44 PM, wuffers m...@wuffers.net wrote:
On r151012 since Nov. And yes, the LUs are exposed via COMSTAR.
If it helps to have some kmem_flags set, I can do that and try to
reproduce it in the
Can confirm that there are problems with Comstar, especially with Fibre/STMF.
Are people seeing problems with iSCSI or does that seem more stable?
-Original Message-
From: OmniOS-discuss [mailto:omnios-discuss-boun...@lists.omniti.com] On Behalf
Of Dan McDonald
Sent: Tuesday, March 24,
On Wed, Mar 25, 2015 at 12:09 PM, Dan McDonald dan...@omniti.com wrote:
Can't I just set this dynamically like so (so I can potentially skip 2
reboots)?
echo kmem_flags/W0xf | mdb -kw
No, because those are read at kmem cache creation time at the system's
start.
Ahh, if I RTFM'd the
On Mar 25, 2015, at 2:17 PM, wuffers m...@wuffers.net wrote:
You reproduce this bug by configuring things a specific way, right? I ask
because you seem to have been running okay until you fell down this
particular panic rabbit hole with a particular set of things, correct?
The panic
On Wed, 25 Mar 2015, Dan McDonald wrote:
;
; On Mar 25, 2015, at 7:31 PM, Andy omn...@citrus-it.net wrote:
;
;
; On Tue, 10 Mar 2015, Dan McDonald wrote:
;
; ; The last bloody didn't have a lot of changes. This one does. Let's go
over them:
; ;
; ; * ipmitool is now 1.8.15
;
; The
On Tue, 10 Mar 2015, Dan McDonald wrote:
; The last bloody didn't have a lot of changes. This one does. Let's go over
them:
;
; * ipmitool is now 1.8.15
The configure.in patch that enabled the open interface was also removed
along with this upgrade to 1.8.15.
On Mar 25, 2015, at 7:31 PM, Andy omn...@citrus-it.net wrote:
On Tue, 10 Mar 2015, Dan McDonald wrote:
; The last bloody didn't have a lot of changes. This one does. Let's go
over them:
;
; * ipmitool is now 1.8.15
The configure.in patch that enabled the open interface was also
+1 John. That documentation would be very welcome.
On Tue, Mar 24, 2015 at 9:50 PM, John Barfield john.barfi...@bissinc.com
wrote:
Actually the numbers I sent for the SmartOS VM to VM test were on a switch
with Jumbo frames (switch = 9216 mtu...SmartOS GZ MTU = 9000) (Extreme
Networks Summit
On Mar 26, 2015, at 12:58 AM, wuffers m...@wuffers.net wrote:
| genunix:kmem_free+1c8 () |
stmf_sbd:sbd_handle_write_same_xfer_completion+14d () |
stmf_sbd:sbd_dbuf_xfer_done+b1 () | stmf:stmf_worker_task+376 () |
unix:thread_start+8 () |
Hmmph. The WRITE_SAME code, huh?
I know
If the LX brand is in I would volunteer with testing different
Linux-Disto's.
Regards
Andreas
On Tue, 24 Mar 2015 05:40:50 +0800, Dan McDonald dan...@omniti.com wrote:
The LX brand hadn't been upstreamed yet. Once it has, we will include
it. We will likely assist in its upstreaming, but
On Mar 25, 2015, at 7:44 PM, Dan McDonald dan...@omniti.com wrote:
I screwed up. The 1.8.15 source has no configure.in. I forgot to replace
the configure.in patch with a similar configure patch.
bloody(build/ipmitool)[2]% /tmp/build_danmcd/ipmitool-1.8.15/src/ipmitool -h
| ggrep -A5
On Wed, Mar 25, 2015 at 2:21 PM, Dan McDonald dan...@omniti.com wrote:
A with-kmem-flags coredump will be very useful.
Here we go. I reproduced this with no load on the SAN, just a DC and
vcenter server up, then created my 10TB disk in the vSphere fat client. As
expected, I got the kernel
13 matches
Mail list logo
