Switch to DuckDuckGo Search
   January 9, 2019  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >

Toggle Join/Part | bottom
[00:03:09] *** strobelight <strobelight!~quassel@2001:420:3042:1320:c19e:2b3f:50e6:e4eb> has quit IRC (Ping timeout: 252 seconds)
[00:06:17] <black_pete> I am yet another person asking about smartos + ZFS + encryption. I've see the ZoL project, and I've compiled ZFS + enryption in a lx branded zone, but I've not been successful building OpenZFS (with or without encryption) in a SmartOS zone. I have built SmartOS using the smartos-live image (*that* took awhile :-) ). I would love some pointers on building OpenZFS on SmartOS (or Illumos; I haven't tried that yet), but failing that, can anyone poi
[00:06:17] <black_pete> me to a resource that discusses the current state of OpenZFS in SmartOS?
[00:21:05] <jbk> there are bugs with zfs encryption that are being fixed
[00:21:43] <jbk> (that appear to be present w/ ZoL as well).. that's the main holdup at this point
[00:24:45] <black_pete> sure, I understand about the incomplete nature of it; I'm still interested in testing it out and working with it
[00:25:33] <jbk> if you still have something setup to build smartos-live
[00:25:40] <black_pete> I do
[00:25:42] <jbk> there should be a file named 'configure-branches'
[00:26:05] <jbk> edit it, and change the 'illumos-joyent: master' line to 'illumos-joyent: zfs-crypto'
[00:26:22] <black_pete> looking for it...
[00:26:23] <jbk> then rerun configure, and rm 0-illumos-stamp
[00:26:37] <jbk> and rebuild
[00:26:55] <jbk> though use at your own risk of course
[00:27:01] <black_pete> oh, naturally
[00:28:31] <jbk> that version's a couple weeks benhind the main branch
[00:28:51] <black_pete> Thanks for the pointers, jbk; re-running configure now
[00:31:16] <black_pete> btw, props to whoever set up building SmartOS; it is by far the easiest software I've built, even if it does take so long on my underpowered test bench machine. :-)
[00:32:19] <jbk> it can take a bit
[00:33:01] <black_pete> that's ok: I have lots of coffee
[00:34:32] <black_pete> re-running the build now
[00:37:05] <black_pete> after this build, I'll have an ISO and a USB key image, but can I use this build to generate an image that I can use to create zones?
[00:37:46] <jbk> you can boot off either and the zfs crypto pieces will be there
[00:37:57] <jbk> though they're not integrated into any tooling other than the zfs command
[00:43:00] <black_pete> ok
[00:45:40] <Smithx10> black_pete: the build process is also being improved
[00:46:02] <Smithx10> https://github.com/joyent/rfd/blob/master/rfd/0145/README.md
[00:47:25] <Smithx10> jbk while demo'ing nat today, my boss was a bit eerie about the nat zone
[00:47:31] <black_pete> Thanks Smithx10. I hadn't see that RFC yet
[00:47:33] <Smithx10> How is the reform nat work going?
[00:48:00] <jbk> it's going
[00:48:03] <Smithx10> I walked him back from the edge when I showed that we would just provision another nat zone on another node if the node couldnt come back up
[00:51:26] <Smithx10> Was the openzfs meeting today?
[00:53:20] <jbk> yes
[00:53:43] <Smithx10> How'd it go I was looking for the video but it wasnt posted yet.... shucks
[00:53:54] <jbk> *shrug* fine
[01:03:17] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has quit IRC (Quit: andy_js)
[01:06:44] *** jellydonut <jellydonut!~jelly@77.16.78.99.tmi.telenormobil.no> has quit IRC (Ping timeout: 244 seconds)
[01:13:00] *** Macer <Macer!macer@unaffiliated/macer> has quit IRC (Read error: Connection reset by peer)
[01:13:16] *** rsully <rsully!~rsully@unaffiliated/rsully> has quit IRC (Quit: rsully)
[01:13:18] *** Macer <Macer!macer@unaffiliated/macer> has joined #smartos
[01:15:02] *** mmlb2 <mmlb2!~mmlb@76-248-148-178.lightspeed.miamfl.sbcglobal.net> has quit IRC (Ping timeout: 258 seconds)
[01:22:12] <LeftWing> It was much more on-agenda than the last meeting!
[01:22:26] <Smithx10> lol, im watching that meeting now
[01:22:39] <Smithx10> Linux vs FreeBSD vs Illumos wars
[01:31:43] <Smithx10> mgerdts: I heard rumors that your migration stuff was working :P :P
[01:36:14] <black_pete> is the video of the openzfs meeting publicly available? If so, where would I find it?
[01:36:25] <Smithx10> https://www.youtube.com/watch?v=TwCc9zjhRw4
[01:36:33] <Smithx10> thats the one i have on in the background right now
[01:37:18] <black_pete> oh, the December one, thanks. I misunderstood and thought you were watching the one from today.
[01:37:53] <black_pete> And then when I couldn't find it; I thought that maybe there was some insider access to it or something :-)
[01:38:56] <Smithx10> i think it should be posted eventually on that youtube channel
[01:39:32] <black_pete> I'll keep an eye on it
[01:39:57] <Smithx10> i think the openzfs twitter account posts when tehy are out
[01:48:11] *** andy_js <andy_js!~andy@50-206-180-2-static.hfc.comcastbusiness.net> has joined #smartos
[02:05:41] *** andy_js <andy_js!~andy@50-206-180-2-static.hfc.comcastbusiness.net> has quit IRC (Quit: andy_js)
[02:12:21] *** andy_js <andy_js!~andy@50-206-180-2-static.hfc.comcastbusiness.net> has joined #smartos
[02:16:50] <Smithx10> Quick questrion, How hard is to move triton admin networks / underlays from /24 to /16
[02:16:53] <Smithx10> or are tehy routable now?
[02:17:18] <Smithx10> and is there a downside to just using a /16 for those non routable networks?
[02:28:53] *** v_a_b <v_a_b!~volker@p57A27DE9.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 244 seconds)
[02:29:24] <bahamat> They're not currently routable like you'd want them to be.
[02:30:28] <bahamat> And resizing a network is problematic. It's not allowed because it would require rebooting every zone on that network to pick up the new prefix length.
[02:46:13] <mgerdts> @Smithx10 I've been little more than a spectator / cheerleader for migration. But yes, it is progressing nicely.
[02:47:20] <Smithx10> mgerdts: Who are the migration champions?
[02:47:44] <Smithx10> bahamat: so.... if I have a new triton deployment going in
[02:47:55] <Smithx10> Should I size for /16 ?
[02:48:03] <Smithx10> to be safe?
[02:48:49] <mgerdts> Todd is primary, Pedro, Orlando, Marsell, and Dylan have some parts of it.
[02:49:49] <Smithx10> Go Todd!!!
[02:50:17] <bahamat> Smithx10: Is this for the underlay or the overlay networks?
[02:50:24] <Smithx10> for admin
[02:50:57] <Smithx10> i guess if i add that many CNs ill need that many networks on the under?
[02:51:04] <Smithx10> well addresses*
[02:51:29] <bahamat> For admin or underlays I (not joyent) use /16's
[02:51:55] *** andy_js <andy_js!~andy@50-206-180-2-static.hfc.comcastbusiness.net> has quit IRC (Quit: andy_js)
[02:51:58] <Smithx10> what / is jpc?
[02:52:12] <bahamat> Joyent uses the allocation our network team provides, which varies
[02:52:25] <Smithx10> guesing depending on the amount nodes?
[02:56:19] <bahamat> More than just that.
[02:56:43] <Smithx10> im doing our first install for the PoC at work tomorrow
[02:56:48] <bahamat> But we're also using rack aware networking now, so our admin network isn't a single flat L2 network anymore, so that changes things a lot.
[02:57:01] <Smithx10> ahhh.... that isn't upstreamed yet?
[02:58:02] <Smithx10> https://github.com/joyent/rfd/blob/master/rfd/0043/README.md
[02:59:54] <Smithx10> is there something i should read before installing that mentions the new features?
[03:02:49] <bahamat> It's fully integrated.
[03:02:59] <bahamat> But, probably not well documented.
[03:03:19] <bahamat> There are several "gotchas", and you need cooperation from the networking gear, Triton can't do this on its own.
[03:03:30] <Smithx10> yea
[03:03:33] <Smithx10> i think ill keep it simple
[03:03:47] <Smithx10> i guess right now for my PoC just do a /16
[03:04:11] <Smithx10> it is possible to change right, but will just require an outage right?
[03:04:30] <bahamat> To do rack aware networking, each rack needs a gateway (ours are L3 switches) that perform DHCP relay, and embed the nic_tag in the dhcp info
[03:04:43] <Smithx10> obviously you guys migrated from flat to per rack
[03:04:58] <Smithx10> gotch, if this goes well i might get some aristas
[03:05:08] <bahamat> But, you need to get the headnode installed with the "base" admin network first, which is not "rack aware".
[03:05:13] <Smithx10> probably the 7160s
[03:05:26] <bahamat> Well, we just added on rack aware racks.
[03:05:42] <Smithx10> gotcha, so base admin /16 is ok yea?
[03:05:45] <bahamat> There's still a core of compute nodes on the base flat admin.
[03:08:35] <bahamat> The Triton stack takes about 40-ish IPs (the exact number depends on add-on components deployed and HA configurations)
[03:08:56] <Smithx10> plus ip per CN right ?
[03:09:04] <bahamat> So that, plus the total number of compute nodes you'll ever grow to before deploying rack aware networking.
[03:09:33] <Smithx10> Im guessing if we sign the contract Joyent will be there to guide us onto that right :)
[03:09:59] <bahamat> realistically, a /24 should be fine, if you're keeping your admin network strictly Triton (i.e., a separate network for switch/router management, etc), which you *should* be doing.
[03:10:07] <Smithx10> We are
[03:10:11] <bahamat> Beyond that, using rack aware networking is probably best.
[03:10:38] <Smithx10> So to increase that admin network / underlay is an outage right
[03:10:47] <Smithx10> not impossible to do
[03:10:54] <Smithx10> but right aware is the way to go
[03:10:56] <bahamat> Well...it's effectively impossible.
[03:11:03] <Smithx10> oh shit
[03:11:16] <Smithx10> Is there a perf hit or something or any reason to not use a bigger address space?
[03:11:21] <bahamat> It's not *really* impossible. But the level of effort involved is...enormous.
[03:13:45] <bahamat> Really, we only use rack aware networking for Manta, which we don't deploy underlays to.
[03:14:19] <Smithx10> a /22 is like 950 or so nodes
[03:14:31] <bahamat> For general compute, where we deploy underlays they are all on the "base" admin network, and we use /16's for the underlays.
[03:15:18] <Smithx10> the underlays arent on a separate vlan?
[03:15:25] <bahamat> They are on a separate vlan
[03:15:56] <bahamat> We have a single prefix that's reused in all datacenters for underlays since they don't route.
[03:16:16] <Smithx10> and for the admin non routable network
[03:16:21] <bahamat> TBH, I'm not sure underlays would support rack aware networking at all.
[03:16:31] <Smithx10> i dont think so
[03:18:02] <jbk> not currently
[03:20:05] <jbk> though it probably wouldn't be _too_ bad to do -- you'd just need each router in your rack to know how to reach all the underlay subnets, and the CNs would need the proper route entries in the GZ routing table
[03:20:44] <jbk> since for the underlay, all that's really happening is sending/receiving UDP datagrams
[03:21:05] <jbk> so as long as the GZ knows where to send a given one, it should work
[03:21:34] <jbk> you'd jst need the bits (not currently implemented) setup to configure a CN
[03:21:38] <jbk> with that info
[03:36:11] *** synegy34 <synegy34!~gatekeep@pe-1-0.wan.rtr1.jmp.cx> has joined #smartos
[03:37:20] *** gatekeep <gatekeep!~gatekeep@pe-1-0.wan.rtr1.jmp.cx> has quit IRC (Ping timeout: 250 seconds)
[03:37:26] *** synegy34 is now known as gatekeep
[03:58:05] *** jubal <jubal!~jubal@247-16-237-24.gci.net> has quit IRC (Ping timeout: 268 seconds)
[04:00:15] *** jubal_ <jubal_!~jubal@247-16-237-24.gci.net> has joined #smartos
[04:04:45] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has quit IRC (Quit: jcea)
[04:18:47] *** tozhu <tozhu!~tozhu@171.223.92.164> has quit IRC (Quit: tozhu)
[04:39:30] *** black_pete <black_pete!~black_pet@gateway.peterguy.com> has quit IRC (Quit: black_pete)
[04:54:37] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[05:18:06] <bahamat> It's not just that, because sapi only has a concept of a single underlay network.
[05:26:59] *** tozhu <tozhu!~tozhu@101.207.125.86> has joined #smartos
[05:29:41] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Quit: Leaving.)
[05:53:28] *** Kurlon_ <Kurlon_!~Kurlon@98.13.72.207> has joined #smartos
[05:54:03] *** Macer_ <Macer_!macer@unaffiliated/macer> has joined #smartos
[05:54:15] *** sjorge_be <sjorge_be!~sjorge@unaffiliated/sjorge> has joined #smartos
[06:02:11] *** Macer <Macer!macer@unaffiliated/macer> has quit IRC (*.net *.split)
[06:02:11] *** Kurlon <Kurlon!~Kurlon@98.13.72.207> has quit IRC (*.net *.split)
[06:02:12] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has quit IRC (*.net *.split)
[06:02:14] *** bdha <bdha!~bdha@165.225.136.186> has quit IRC (*.net *.split)
[06:02:21] *** Macer_ is now known as Macer
[06:02:21] *** sjorge_be is now known as sjorge
[06:03:52] *** Latr_work <Latr_work!uid4039@gateway/web/irccloud.com/x-xzqrnvbgqsleksuj> has quit IRC (Quit: Connection closed for inactivity)
[06:54:33] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[06:57:07] *** black_pete <black_pete!~black_pet@gateway.peterguy.com> has joined #smartos
[07:13:58] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Quit: Leaving.)
[07:26:08] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has joined #smartos
[07:52:50] *** tozhu <tozhu!~tozhu@101.207.125.86> has quit IRC (Quit: tozhu)
[07:54:32] *** tozhu <tozhu!~tozhu@101.207.125.86> has joined #smartos
[08:15:12] *** v_a_b <v_a_b!~volker@p57A27D60.dip0.t-ipconnect.de> has joined #smartos
[08:34:37] *** black_pete <black_pete!~black_pet@gateway.peterguy.com> has quit IRC (Quit: black_pete)
[08:36:06] *** mno-hime <mno-hime!~mno-hime@94.142.238.232> has quit IRC (Quit: Leaving)
[08:55:45] *** JeanParpaillon <JeanParpaillon!~jean@176.164.1.146> has joined #smartos
[09:03:25] *** lgtaube <lgtaube!~lgt@46.165.251.115> has quit IRC (Read error: Connection reset by peer)
[09:31:19] *** bens1 <bens1!~bens1@161.122.2.81.in-addr.arpa> has joined #smartos
[09:34:37] *** JeanParpaillon <JeanParpaillon!~jean@176.164.1.146> has quit IRC (Ping timeout: 244 seconds)
[09:34:37] *** tozhu <tozhu!~tozhu@101.207.125.86> has quit IRC (Quit: tozhu)
[09:55:43] *** jubal <jubal!~jubal@64-16-237-24.gci.net> has joined #smartos
[09:57:33] *** jubal_ <jubal_!~jubal@247-16-237-24.gci.net> has quit IRC (Ping timeout: 245 seconds)
[10:25:59] *** man_u <man_u!~manu@manu2.gandi.net> has joined #smartos
[10:45:35] *** mzf <mzf!~fakhraee@unaffiliated/mzf> has joined #smartos
[11:13:25] *** insane^ <insane^!~insane@fw.vispiron.de> has joined #smartos
[11:23:40] *** jellydonut <jellydonut!~jelly@77.18.51.32.tmi.telenormobil.no> has joined #smartos
[11:28:57] *** insane^ <insane^!~insane@fw.vispiron.de> has quit IRC (Read error: Connection reset by peer)
[11:36:37] *** insane^ <insane^!~insane@fw.vispiron.de> has joined #smartos
[12:04:56] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has quit IRC (Remote host closed the connection)
[12:06:06] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has joined #smartos
[12:06:19] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has quit IRC (Remote host closed the connection)
[12:06:47] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has joined #smartos
[12:46:27] *** jubal <jubal!~jubal@64-16-237-24.gci.net> has quit IRC (Remote host closed the connection)
[12:49:43] *** jubal <jubal!~jubal@64-16-237-24.gci.net> has joined #smartos
[12:59:34] *** strobelight <strobelight!~quassel@c-69-180-7-202.hsd1.ga.comcast.net> has joined #smartos
[13:04:41] *** neuroserve <neuroserve!~toens@195.71.113.124> has joined #smartos
[13:30:13] *** strobelight_ <strobelight_!~quassel@2001:420:c0c8:1004::a5> has joined #smartos
[13:30:13] *** strobelight is now known as Guest11639
[13:31:16] *** strobelight_ is now known as strobelight
[13:34:03] *** Guest11639 <Guest11639!~quassel@c-69-180-7-202.hsd1.ga.comcast.net> has quit IRC (Ping timeout: 268 seconds)
[13:45:02] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has quit IRC (Ping timeout: 246 seconds)
[13:47:29] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has joined #smartos
[13:59:20] *** jcea <jcea!~Thunderbi@2001:41d0:1:8a82:7670:6e00:7670:6e00> has joined #smartos
[14:00:26] *** jellydonut <jellydonut!~jelly@77.18.51.32.tmi.telenormobil.no> has quit IRC (Read error: Connection reset by peer)
[14:29:53] *** jubal <jubal!~jubal@64-16-237-24.gci.net> has quit IRC (Read error: Connection reset by peer)
[14:33:13] *** jubal <jubal!~jubal@247-16-237-24.gci.net> has joined #smartos
[14:35:40] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has joined #smartos
[14:49:47] *** mgerdts <mgerdts!~textual@96-41-228-208.dhcp.ftbg.wi.charter.com> has quit IRC (Ping timeout: 246 seconds)
[15:05:32] *** gh34 <gh34!~textual@rrcs-162-155-144-114.central.biz.rr.com> has joined #smartos
[15:08:31] *** mgerdts <mgerdts!~textual@137-027-069-158.biz.spectrum.com> has joined #smartos
[15:19:33] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has joined #smartos
[15:20:33] *** hotbox <hotbox!~hotbox@2001:41d0:fe8f:b70a:20d:b9ff:fe47:7c05> has quit IRC (Ping timeout: 252 seconds)
[15:22:37] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[15:25:36] *** hotbox <hotbox!~hotbox@2001:41d0:fe8f:b70a:20d:b9ff:fe47:7c05> has joined #smartos
[15:27:56] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Quit: Leaving.)
[15:33:24] *** Kurlon_ <Kurlon_!~Kurlon@98.13.72.207> has quit IRC (Remote host closed the connection)
[15:34:00] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #smartos
[15:41:12] *** chorrell <chorrell!~chorrell@unaffiliated/chorrell> has joined #smartos
[16:05:56] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has quit IRC (Quit: andy_js)
[16:13:19] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has joined #smartos
[16:14:04] <Smithx10> I bought a DL 380, which has 6 MINI sas connectors in the backplane, and my HBA has only 4 MiniHD Slots..... It seems there are only 2 mini sas ports per 8 drives
[16:14:33] <Smithx10> I cant access the last 8 drives right now because the cabling kit I was shipped only connects 16 of the drives to the hba.... but the hba can support up to 1024 devices
[16:14:56] <Smithx10> Is there a MiniSasHD to SAS Expander that I should use?
[16:20:12] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has quit IRC (Read error: Connection reset by peer)
[16:35:45] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has joined #smartos
[16:40:56] <rmustacc> Smithx10: What generation of HP box?
[16:41:05] <Smithx10> dl 380 gen 10
[16:41:20] <rmustacc> We don't support the Smart* HBAs in that line.
[16:41:29] <Smithx10> Yeah I bought LSI hbas
[16:41:31] <Smithx10> 9305i
[16:41:44] <Smithx10> https://www.broadcom.com/products/storage/host-bus-adapters/sas-9305-16i#overview
[16:42:00] <rmustacc> When the HBA can support up to 1024 drives like it mentions, that's through an expander.
[16:42:26] <Smithx10> so that HP Expander would have to be better
[16:42:47] <Smithx10> and maybe wire up more than 4 drives per connection
[16:42:55] <Smithx10> or is that 2nd sas connection just for redundancy ?
[16:44:42] *** insane^ <insane^!~insane@fw.vispiron.de> has quit IRC (Ping timeout: 250 seconds)
[16:45:43] *** polishdub <polishdub!~polishdub@207.86.38.254> has joined #smartos
[16:46:10] *** mgerdts <mgerdts!~textual@137-027-069-158.biz.spectrum.com> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
[16:57:40] *** mgerdts <mgerdts!~textual@2600-6c44-0c7f-ec89-6da2-dbc4-2de5-2325.dhcp6.chtrptr.net> has joined #smartos
[17:01:59] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[17:12:01] *** black_pete <black_pete!~black_pet@gateway.peterguy.com> has joined #smartos
[17:13:15] <ismell> I got a used Intel RES2SV240 I should probably sell if anyone is interested
[17:13:49] <ismell> stopped using it because using sata drives with a sas expander was a bad idea
[17:14:14] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has quit IRC (Quit: andy_js)
[17:31:16] *** andy_js <andy_js!~andy@static-108-31-135-162.washdc.fios.verizon.net> has joined #smartos
[17:43:12] *** neuroserve <neuroserve!~toens@195.71.113.124> has quit IRC (Ping timeout: 250 seconds)
[18:14:36] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has quit IRC (Ping timeout: 252 seconds)
[18:19:44] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has joined #smartos
[18:23:42] *** mno-hime <mno-hime!~mno-hime@94.142.238.232> has joined #smartos
[18:33:41] *** chorrell <chorrell!~chorrell@unaffiliated/chorrell> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)
[18:43:14] *** man_u <man_u!~manu@manu2.gandi.net> has quit IRC (Ping timeout: 246 seconds)
[18:49:28] *** bens1 <bens1!~bens1@161.122.2.81.in-addr.arpa> has quit IRC (Quit: bens1)
[19:00:37] *** Gathis <Gathis!~TheBlack@unaffiliated/gathis> has joined #smartos
[19:05:18] *** synegy34 <synegy34!~gatekeep@pe-1-0.wan.rtr1.jmp.cx> has joined #smartos
[19:06:49] *** gatekeep <gatekeep!~gatekeep@pe-1-0.wan.rtr1.jmp.cx> has quit IRC (Ping timeout: 246 seconds)
[19:06:53] *** synegy34 is now known as gatekeep
[19:46:26] <adam_vollrath> Can any SmartOS VM have a virtual interface in promiscuous mode?
[19:46:56] *** chorrell <chorrell!~chorrell@unaffiliated/chorrell> has joined #smartos
[19:53:29] <greenline> We've noted that sometimes an update causes a library to get upgraded, but all packages depending on that library are not necessarily updated, and then fail.
[19:54:01] <greenline> For example, after updating repos and doing upgrades, mariadb was not updated (I guess because the version did not change between repos), but was built against a newer ncurses.
[19:54:06] <greenline> so then it breaks at runtime.
[20:03:23] *** mnowak_ <mnowak_!mnowak_@nat/suse/x-fbcgcelnhwhjwzrr> has quit IRC (Ping timeout: 245 seconds)
[20:05:38] *** mnowak_ <mnowak_!mnowak_@nat/suse/x-iifxzwlzdlfsascj> has joined #smartos
[20:07:19] *** JeanParpaillon <JeanParpaillon!~jean@176.164.125.94> has joined #smartos
[20:15:57] <mattronix> hi yall
[20:23:53] <jperkin> greenline: is that with an older release? newer versions of pkgin should avoid such problems
[20:41:06] <Smithx10> rmustacc: just for note the onboard on this machine gen10 is HPE Smart Array P816i-a SR Gen10
[20:56:29] *** chorrell <chorrell!~chorrell@unaffiliated/chorrell> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
[21:01:22] <greenline> jperkin: I believe it was a 2014 or 2015 to 2016Q4 release upgrade
[21:02:49] <jperkin> greenline: yeh, pkgin fixes are in 2018Q2 onwards
[21:03:59] *** JeanParpaillon <JeanParpaillon!~jean@176.164.125.94> has quit IRC (Quit: JeanParpaillon)
[21:04:16] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has quit IRC (Ping timeout: 250 seconds)
[21:06:53] <Smithx10> booting smartos on a dl 380 gen 10.... ./crosses fingers.
[21:08:25] <Smithx10> lots of ............
[21:10:58] <adam_vollrath> This is what I'm looking for https://technotes.seastrom.com/2016/03/04/sniffing-on-smartos.html
[21:12:03] *** jellydonut <jellydonut!~jelly@77.18.49.241.tmi.telenormobil.no> has joined #smartos
[21:12:13] <Smithx10> I saw an error about sof error interurpts from the USB controller
[21:13:28] <Smithx10> Guessing I need to set the usb contorller to some legacy mode or something
[21:13:32] <Smithx10> its an internal USB controller
[21:19:03] <Smithx10> definitely saw this.....
[21:19:03] <Smithx10> 2015-12-30T09:52:35.452663+00:00 compute1 usba: [ID 691482 kern.warning] WARNING: /pci@0,0/pci1af4,1100@1,2 (uhci0): No SOF interrupts have been received, this USB UHCI host controller is unusable
[21:19:03] <Smithx10> :(
[21:36:18] *** fejfighter <fejfighter!~fejfighte@124-171-205-37.dyn.iinet.net.au> has quit IRC (Ping timeout: 245 seconds)
[21:44:14] <Smithx10> will that cause the installer to be unresponsive ?
[21:45:11] <jbk> what type of machine is that?
[21:53:59] <greenline> I was attempting sdcadm expertimental update-other and had it crash with an uncaught assertionerror
[22:02:38] <Smithx10> i got to a shell through ipmi
[22:02:53] <Smithx10> and the usb disk is there
[22:04:34] *** rsully <rsully!~rsully@unaffiliated/rsully> has joined #smartos
[22:09:50] <Smithx10> im gonna try mounting it and writing to it
[22:12:13] <Smithx10> disk info is printing out failed to get LAN config
[22:27:03] <Smithx10> Is there LLDP command in SmartOS to see what VLANs are available on my link?
[22:32:22] <rsully> Are there still issues on smartos with 4Kn drives? is anyone here using them?
[22:56:29] *** yomisei <yomisei!~void@ip4d16bd91.dynamic.kabel-deutschland.de> has quit IRC (Ping timeout: 244 seconds)
[22:59:06] *** Kurlon_ <Kurlon_!~Kurlon@98.13.72.207> has joined #smartos
[23:01:28] *** gh34 <gh34!~textual@rrcs-162-155-144-114.central.biz.rr.com> has quit IRC (Quit: Textual IRC Client: www.textualapp.com)
[23:02:07] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 240 seconds)
[23:11:48] <greenline> I'm unsure how to proceed if sdcadm experimental update-other fails. Presumably at this point it is not safe to move on to platform image upgrade...
[23:16:51] <Smithx10> jbk: good news.... Looks like im booting off the internal usb in the dl380g10
[23:17:14] <Smithx10> seems those errors dont stop me from mounting, reading and writing
[23:19:16] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Quit: Leaving.)
[23:32:12] *** yomisei <yomisei!~void@ip4d16bd91.dynamic.kabel-deutschland.de> has joined #smartos
[23:34:12] *** kkantor <kkantor!~kkantor@c-24-118-59-107.hsd1.mn.comcast.net> has quit IRC (Ping timeout: 250 seconds)
[23:54:31] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[23:54:36] *** polishdub <polishdub!~polishdub@207.86.38.254> has quit IRC (Remote host closed the connection)
[23:55:07] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Client Quit)
[23:55:34] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[23:57:10] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Client Quit)
[23:58:22] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has joined #smartos
[23:59:44] *** ingenthr <ingenthr!~ingenthr@47.150.244.29> has quit IRC (Client Quit)
top

   January 9, 2019  
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | >