August 18, 2016 
< | 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 | >
August 18, 2016 [00:11:33] *** natkin <natkin!~natkin@66.187.75.122> has joined #omnios[00:12:09] *** lextt <lextt!~l3xtt@95.215.44.99> has quit IRC (Read error: Connection reset by peer)[00:14:54] *** andy_js <andy_js!~andy@90.219.225.136> has quit IRC (Quit: andy_js)[00:14:56] *** xzi11a <xzi11a!~robert@static-108-48-124-82.washdc.fios.verizon.net> has quit IRC (Ping timeout: 265 seconds)[00:15:16] *** Kurlon <Kurlon!~Kurlon@cpe-104-228-216-170.maine.res.rr.com> has joined #omnios[00:16:26] *** lextt <lextt!~lextt@95.215.44.99> has joined #omnios[00:17:32] *** natkin <natkin!~natkin@66.187.75.122> has quit IRC (Ping timeout: 240 seconds)[00:19:50] *** natkin <natkin!~natkin@rrcs-24-173-253-235.sw.biz.rr.com> has joined #omnios[00:19:58] *** natkin <natkin!~natkin@rrcs-24-173-253-235.sw.biz.rr.com> has quit IRC (Remote host closed the connection)[00:20:24] *** natkin <natkin!~natkin@162.218.228.196> has joined #omnios[00:24:52] *** arekinath <arekinath!~quassel@pdpc/supporter/professional/arekinath> has quit IRC (Remote host closed the connection)[00:25:09] *** theason <theason!~theason@207.65.77.126> has quit IRC (Ping timeout: 276 seconds)[00:25:17] *** theason_ <theason_!~theason@207.65.77.126> has joined #omnios[00:25:48] *** wonko <wonko!~wonko@wiggum.4amlunch.net> has quit IRC (Ping timeout: 276 seconds)[00:26:04] *** arekinath <arekinath!~quassel@pdpc/supporter/professional/arekinath> has joined #omnios[00:40:08] *** dmip <dmip!~Thunderbi@84.51.125.126> has quit IRC (Ping timeout: 250 seconds)[00:40:58] *** wonko <wonko!~wonko@wiggum.4amlunch.net> has joined #omnios[00:45:48] *** natkin <natkin!~natkin@162.218.228.196> has quit IRC (Remote host closed the connection)[00:50:07] *** pjy <pjy!~pjy@pool-108-45-119-127.washdc.fios.verizon.net> has quit IRC (Ping timeout: 252 seconds)[00:53:46] *** pjy <pjy!~pjy@pool-108-45-119-127.washdc.fios.verizon.net> has joined #omnios[01:16:07] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has joined #omnios[01:23:23] *** theason <theason!~theason@207.65.77.126> has joined #omnios[01:26:15] *** theason_ <theason_!~theason@207.65.77.126> has quit IRC (Ping timeout: 276 seconds)[02:16:50] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has quit IRC (Ping timeout: 250 seconds)[02:27:42] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has joined #omnios[02:28:21] *** pjy <pjy!~pjy@pool-108-45-119-127.washdc.fios.verizon.net> has quit IRC (Quit: Leaving.)[02:49:32] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has quit IRC (Quit: Leaving.)[02:49:53] *** pjy <pjy!~pjy@pool-108-45-119-127.washdc.fios.verizon.net> has joined #omnios[02:50:10] *** pjy <pjy!~pjy@pool-108-45-119-127.washdc.fios.verizon.net> has left #omnios[02:54:08] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has joined #omnios[02:58:02] *** ira <ira!~ira@samba/team/ira> has quit IRC (Quit: Leaving)[02:58:03] *** v_a_b1 <v_a_b1!~volker@p5B3712CF.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 264 seconds)[02:58:03] *** v_a_b <v_a_b!~volker@p5B3712CF.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 264 seconds)[03:01:15] *** v_a_b <v_a_b!~volker@p5B371158.dip0.t-ipconnect.de> has joined #omnios[03:02:10] *** v_a_b1 <v_a_b1!~volker@p5B371158.dip0.t-ipconnect.de> has joined #omnios[03:14:46] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has quit IRC (Ping timeout: 252 seconds)[03:33:04] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has quit IRC (Quit: Leaving.)[03:37:25] *** cyterian|2 <cyterian|2!~kvirc@ipservice-092-211-198-218.092.211.pools.vodafone-ip.de> has joined #omnios[03:40:59] *** cyterian <cyterian!~kvirc@ipservice-092-217-098-089.092.217.pools.vodafone-ip.de> has quit IRC (Ping timeout: 260 seconds)[04:27:51] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[04:59:44] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 258 seconds)[05:30:14] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has joined #omnios[05:34:37] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has quit IRC (Ping timeout: 258 seconds)[06:22:08] *** chrustler <chrustler!~chrustler@94-137-110-36.customers.ownit.se> has quit IRC (Remote host closed the connection)[06:36:44] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has joined #omnios[06:39:03] *** chrustler <chrustler!~chrustler@94-137-110-36.customers.ownit.se> has joined #omnios[06:53:32] *** matejz <matejz!~matejz@element.planetq.org> has joined #omnios[06:55:04] *** synegy34 <synegy34!~gatekeep@pe-1-0.wan.rtr1.circlesoftus.org> has quit IRC (Ping timeout: 258 seconds)[06:55:30] *** gatekeep <gatekeep!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has joined #omnios[06:55:30] *** gatekeep <gatekeep!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has quit IRC (Changing host)[06:55:30] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has joined #omnios[06:56:26] *** matejz <matejz!~matejz@element.planetq.org> has quit IRC (Client Quit)[07:05:44] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has quit IRC (Quit: Leaving.)[07:13:37] *** Botanic <Botanic!~Botanic@tita/admin/Botanic> has joined #omnios[07:20:28] *** matejz <matejz!~matejz@cgn-nat-188-64-25-239.simobil.net> has joined #omnios[07:23:25] *** matejz <matejz!~matejz@cgn-nat-188-64-25-239.simobil.net> has quit IRC (Client Quit)[07:29:08] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has joined #omnios[07:58:37] *** slx86 <slx86!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has joined #omnios[08:02:48] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has quit IRC (Quit: Leaving.)[08:03:16] *** matejz <matejz!~matejz@141.255.254.208> has joined #omnios[08:31:04] *** dmip <dmip!~Thunderbi@84.51.125.126> has joined #omnios[08:44:09] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has quit IRC (Ping timeout: 250 seconds)[08:44:50] *** Toasterson <Toasterson!~toast@68.30.150.83.dyn.dsl.as8758.net> has joined #omnios[08:45:01] *** gatekeep <gatekeep!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has joined #omnios[08:45:01] *** gatekeep <gatekeep!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has quit IRC (Changing host)[08:45:01] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has joined #omnios[09:06:26] *** slx86 <slx86!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has quit IRC (Quit: slx86)[09:40:13] *** andy_js <andy_js!~andy@90.219.225.136> has joined #omnios[09:47:43] *** wiedi <wiedi!~wiedi@ip5b41bdb7.dynamic.kabel-deutschland.de> has quit IRC (Quit: ^C)[09:54:08] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[09:54:20] *** ptribble <ptribble!~ptribble@cpc92320-cmbg19-2-0-cust3282.5-4.cable.virginm.net> has joined #omnios[09:58:21] *** dasjoe <dasjoe!~dasjoe@americangirlscouts.org> has quit IRC (Excess Flood)[09:58:40] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 258 seconds)[09:59:45] *** dasjoe <dasjoe!~dasjoe@americangirlscouts.org> has joined #omnios[10:38:18] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[10:42:45] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 258 seconds)[11:02:01] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[11:13:39] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 264 seconds)[11:17:38] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[11:22:24] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 260 seconds)[11:38:16] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has joined #omnios[11:42:49] *** tozhu <tozhu!~Thunderbi@119.6.113.95> has quit IRC (Ping timeout: 260 seconds)[14:55:33] *** Kurlon <Kurlon!~Kurlon@cpe-104-228-216-170.maine.res.rr.com> has quit IRC (Ping timeout: 240 seconds)[14:59:36] *** ira <ira!ira@samba/team/ira> has joined #omnios[15:20:43] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has joined #omnios[15:24:59] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has quit IRC (Ping timeout: 250 seconds)[15:31:01] *** happy-dude <happy-dude!uid62780@gateway/web/irccloud.com/x-humbxrvknlpszwmj> has joined #omnios[15:41:49] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has joined #omnios[15:47:52] *** Izaac <Izaac!~izaac@janek.setec.org> has joined #omnios[15:55:10] *** baojg <baojg!~baojg@107.170.0.159> has joined #omnios[15:56:51] *** baojg <baojg!~baojg@107.170.0.159> has quit IRC (Remote host closed the connection)[16:03:44] *** matejz <matejz!~matejz@141.255.254.208> has quit IRC (Quit: matejz)[16:21:24] *** daleg_ <daleg_!~daleg@pool-71-163-238-201.washdc.fios.verizon.net> has joined #omnios[16:25:21] *** xzi11a <xzi11a!~robert@static-108-48-124-82.washdc.fios.verizon.net> has joined #omnios[16:39:43] *** Toasterson <Toasterson!~toast@68.30.150.83.dyn.dsl.as8758.net> has quit IRC (Ping timeout: 244 seconds)[16:51:53] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has joined #omnios[16:53:36] <justif> is it possible/advisable to change volblocksize on an existing zvol?[16:56:04] <danmcd> It's not possible.[16:56:15] <danmcd> And I quote from the zfs(1M) command man page:[16:56:30] <danmcd> For volumes, specifies the block size of the[16:56:30] <danmcd> volume. The blocksize cannot be changed once the[16:56:32] <danmcd> volume has been written, so it should be set at[16:56:33] <danmcd> volume creation time. The default blocksize for[16:56:34] <danmcd> volumes is 8 Kbytes. Any power of 2 from 512 bytes[16:56:35] <danmcd> to 128 Kbytes is valid.[16:57:04] <richlowe> also, it's not possible because it's not possible.[16:57:12] <richlowe> not just an implementation choice[16:58:49] <justif> ok thanks[17:06:43] <justif> from an iostat -En I see this line[17:06:45] <justif> Illegal Request: 528 Predictive Failure Analysis: 0[17:07:10] <justif> havent found anything definitive on what illegal request means[17:08:54] <richlowe> think it's literally the SCSI sense key (or a simulacrum, if ATA/SATA/etc.)[17:09:03] <daleg_> it means a command issued to the drive that the drive rejected[17:09:11] <daleg_> these are actually kind of normal to see[17:09:14] <justif> ok[17:09:27] <justif> still seem to be having performance issues with these SSDs[17:09:29] <daleg_> sometimes they're the result of the driver testing the drive for features[17:09:42] <justif> extended device statistics[17:09:42] <justif> r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device[17:09:42] <justif> 0.0 84.0 0.0 4223.6 0.0 0.7 0.0 8.0 0 28 c1t0d1[17:09:42] <justif> 0.0 90.0 0.0 4619.6 0.0 1.2 0.0 13.3 0 52 c1t1d1[17:09:42] <justif> 0.0 128.0 0.0 8843.2 0.0 1.9 0.0 14.6 0 54 vm_tank[17:11:05] <daleg_> drive firmware is a murky murky place where visibility disappears completely... what kind of ssds are these?[17:11:19] <justif> Vendor: SanDisk Product: LT0400WM Revision: D414[17:11:30] <justif> SAS write intensive[17:11:59] <daleg_> so SanDisk Optimus Max series SSDs?[17:15:35] <daleg_> http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=4XWDY&fileId=3548204141&osCode=WS8R2&productCode=poweredge-r620&languageCode=en&categoryId=AS[17:15:53] <daleg_> they seem to have been loaded with the most recent firmware as offered on dell's site[17:15:59] <justif> yup[17:16:08] <justif> that was an ordeal in itself[17:16:14] <daleg_> although those patch notes aren't encouraging :V[17:16:46] <justif> no[17:16:54] <daleg_> are you seeing any scsi command timeouts in /var/adm/messages ?[17:17:31] <justif> nope[17:20:28] <daleg_> what kind of sas controller are these hanging off of?[17:20:41] <justif> dell h730 in hba mode[17:21:37] <daleg_> oh boy[17:22:02] <justif> ?[17:22:16] <daleg_> dell's perc controllers have always been problematic[17:22:43] <justif> the ones in our amsterdam DC with Toshiba ssds are working just fine[17:22:51] <justif> but in the meantime can I remove them as a mirrored log device by setting sync=disabled for the pool and then removing that mirror?[17:23:10] <justif> would that be safe for active IO?[17:29:23] *** Toasterson <Toasterson!~toast@2a02:aa10:e100:4b00:3798:d028:fa3e:2cf8> has joined #omnios[17:29:28] <danmcd> Yes. It'll slow things down, but yes.[17:46:52] <justif> things are already slow[17:58:56] *** matejz <matejz!~matejz@element.planetq.org> has joined #omnios[18:00:05] <justif> since I am using the ssds as a log device would it make sense to partition a section of it off since 400 is a little big?[18:01:45] <danmcd> Yeah... and then the wear-balancing of the SSDs can make your smaller version last longer.[18:02:50] <justif> could that also help the performance?[18:10:51] *** matejz <matejz!~matejz@element.planetq.org> has quit IRC (Quit: matejz)[18:23:52] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has quit IRC (Remote host closed the connection)[18:32:27] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has joined #omnios[18:35:39] *** natkin <natkin!~natkin@104-8-25-179.lightspeed.snantx.sbcglobal.net> has quit IRC (Remote host closed the connection)[18:52:59] *** daleg_ <daleg_!~daleg@pool-71-163-238-201.washdc.fios.verizon.net> has quit IRC ()[19:06:45] *** chrustler <chrustler!~chrustler@94-137-110-36.customers.ownit.se> has quit IRC (Remote host closed the connection)[19:07:31] <patdk-wk> it's pointless to section a part off[19:07:37] <patdk-wk> unless you secure erase them, then partition them[19:08:04] <patdk-wk> it should only help performance if the ssd firmware is crappy[19:11:54] *** ira <ira!ira@samba/team/ira> has quit IRC (Quit: Leaving)[19:16:27] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has joined #omnios[19:38:49] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has quit IRC (Ping timeout: 260 seconds)[19:39:05] *** sjorge <sjorge!~sjorge@unaffiliated/sjorge> has joined #omnios[19:41:47] *** chrustler <chrustler!~chrustler@94-137-110-36.customers.ownit.se> has joined #omnios[19:50:26] *** matejz <matejz!~matejz@element.planetq.org> has joined #omnios[20:01:55] *** matejz <matejz!~matejz@element.planetq.org> has quit IRC (Quit: matejz)[20:02:55] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has quit IRC (Read error: Network is unreachable)[20:03:19] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has joined #omnios[20:10:10] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has joined #omnios[20:14:33] *** tozhu <tozhu!~Thunderbi@218.88.84.11> has quit IRC (Ping timeout: 240 seconds)[20:19:49] *** matejz <matejz!~matejz@element.planetq.org> has joined #omnios[20:24:16] *** matejz <matejz!~matejz@element.planetq.org> has quit IRC (Client Quit)[20:56:15] *** slx86 <slx86!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has joined #omnios[21:00:43] <justif> any reason why I get numbers like this when my ssds are just in a mirror pooled and writing directly to them but nothing like that when used as a log device?[21:01:31] <justif> https://www.irccloud.com/pastebin/r431r50Z/[21:07:46] <patdk-wk> cause log device requires flushing each write[21:07:53] <patdk-wk> just in a pool doesn't flush the writes[21:08:08] <patdk-wk> unless you have sync=always[21:08:38] <justif> so the ssd could be bad flushing the writes?[21:08:42] <justif> *at[21:08:54] <patdk-wk> yes[21:09:03] <justif> anyway to confirm that?[21:09:16] <patdk-wk> sync=always?[21:09:43] <patdk-wk> while using the ssd's as a normal pool device, not log[21:10:05] <patdk-wk> that will cause each write to get flushed[21:10:14] <patdk-wk> so the issue should come back, like using them for a log device[21:12:01] <justif> https://www.irccloud.com/pastebin/DAicEMLN/[21:12:28] <justif> so definitely worse[21:12:53] <justif> thats with just a simple dd if of[21:13:07] <patdk-wk> not horrible though, 3ms[21:13:14] <patdk-wk> not like it was before around 13ms[21:13:18] *** danmcd <danmcd!~danmcd@static-71-174-113-16.bstnma.fios.verizon.net> has quit IRC (Quit: danmcd)[21:13:20] <justif> yea[21:13:32] <patdk-wk> 3ms is still not good, but :)[21:13:49] <justif> but it only gets to 13 when using it as a log device[21:16:58] <justif> https://www.irccloud.com/pastebin/kMcxCg27/[21:17:20] <justif> this is one of the other boxes that has toshiba ssds[21:17:30] <justif> 0 and 1 are the ssds[21:18:20] <patdk-wk> that is different from the other day[21:18:25] <patdk-wk> that shows the ssd's behaving[21:18:34] <patdk-wk> just the pool is slow[21:18:50] <patdk-wk> how is the pool built?[21:19:17] <justif> this last paste if from a server without issue[21:19:22] <patdk-wk> ah :)[21:19:47] <justif> so there are 4 boxes total[21:19:49] <justif> 2 per dc[21:20:52] <justif> all 4 are dell 730xd with 20 1.2T SAS 10k 2 400T SAS write intensive[21:21:01] <justif> 128G per box[21:21:09] <justif> 10G networking[21:21:35] <justif> the good boxes have toshiba SSDs and the bad ones have SanDisk SSDs[21:23:42] <daleg> this kind of problem can't be really solved unless we can get some low-level scsi bus activity going on[21:23:58] <daleg> you mentioned the Illegal Request counter earlier[21:24:13] <daleg> while it's normal to see that increment over time, it does seem rather high[21:24:39] <daleg> which makes me wonder if these sandisk drives lack a feature or are poorly responding to a command[21:25:00] <justif> yea the good boxes have the counts also but not nearly as high and has production running on it[21:25:01] <daleg> s/bus activity/bus monitoring and snooping[21:25:55] <daleg> SSDs these days can be such a paint[21:25:58] <daleg> pain, even[21:26:48] <daleg> before, few manufacturers were in the storage business because of the mechanical nature of the drives demanded really specialized people, lots of R&D, and really tight manufacturing standards.... so there were only a few players[21:27:58] <daleg> now with SSDs, anyone who thinks they can design a pcb and pay a component manufacturer to shove some chips onto it are getting into the game, often with lackluster firmware and without the years of institutional knowledge that the traditional spinning rust makers have[21:32:45] <daleg> I'm wondering something[21:32:58] <justif> ok[21:33:28] <daleg> if you could boot like, a Alpine linux ISO just to use hdparm to grab the low-level feature and option stats from the drives[21:34:05] <daleg> perhaps these were shipped with any local caches turned off because dell put them behind a PERC card[21:34:33] <daleg> Dell has been known to do things like that[21:34:45] <daleg> in an attempt to be helpful, I suppose[21:40:08] <justif> hmm, need to move data off it but that has been slow[21:40:23] <justif> could I get that info with format -e[21:42:05] <daleg> no, that's not detailed enough. hdparm will allow you to get command set support, cache sizes and status, cache configuration and so forth[21:42:18] <daleg> I really wish we had an equivalent utility[21:42:32] *** natkin <natkin!~natkin@cpe-70-117-102-168.austin.res.rr.com> has joined #omnios[21:42:49] <daleg> it would be a really nifty project for someone with the time and inclination[21:44:00] <daleg> oh you know what[21:44:53] <daleg> what's the block size on these drives?[21:45:37] <daleg> oddly sandisk's datasheets on them don't say[21:45:37] <justif> how could I confirm?[21:46:01] <patdk-wk> there is no accurate way[21:46:11] <patdk-wk> other than to open it up, and check the chips used[21:47:05] <daleg> man, sandisk's site for these products just scream "we're a newcomer here"[21:47:09] *** natkin <natkin!~natkin@cpe-70-117-102-168.austin.res.rr.com> has quit IRC (Ping timeout: 260 seconds)[21:47:16] <justif> yup[21:47:27] <daleg> the datasheets are just dressed-up marketing hand-outs[21:47:32] <patdk-wk> ya, but those ssd's are some of the oldest around[21:47:42] <patdk-wk> wasn't sandisk just bought?[21:48:58] <patdk-wk> ya, wdc owns them now[21:49:42] <daleg> hmm[21:49:43] <daleg> http://downloads.sandisk.com/downloads/ess/optimus-max-product-specs.pdf[21:49:50] <daleg> according to this, they're indeed 512[21:50:02] <daleg> but I'm not sure if this rev of the document is current[21:50:17] <daleg> ah, june 2016.. relatively current I'd say[21:50:56] <daleg> ok, that's good. I was wondering if you might be running into some 512 vs. 4k[21:51:28] <daleg> and even still you can't trust some drives that say they're 512, because they're 4k under the sheets[21:51:33] <justif> not sure that is the same disk since that one states 3.8T or series[21:52:37] <justif> https://www.sandisk.com/business/datacenter/products/flash-devices/ssds/sas-ssd/lightning-gen2[21:52:58] <justif> I wanna say its an ascend or an ultra[21:56:28] <daleg> sector sizes supported: 512, 520, or 4k[21:56:49] <patdk-wk> ya, but that is just firmware sector size[21:56:51] <patdk-wk> not the real pagesize[21:57:22] <daleg> yeah... and even if it was a sector size issue, it still wouldn't really explain the large amounts of illegal requests[21:57:32] <daleg> which are suspect in and of themselves[22:06:29] <daleg> I wish I could help you more justif, but I don't think I can without actually having one of these drives to snoop around on[22:06:59] <justif> yea gonna pester dell to replace them with the Toshibas[22:07:42] <daleg> you could drop a query on the omnios-discuss mailing list or the illumos discuss one asking if anyone else has these drives and what their observations are[22:08:05] <justif> OK I think I will do that[22:08:51] *** Toasterson <Toasterson!~toast@2a02:aa10:e100:4b00:3798:d028:fa3e:2cf8> has quit IRC (Ping timeout: 264 seconds)[22:16:51] *** slx87 <slx87!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has joined #omnios[22:17:03] *** Botanic <Botanic!~Botanic@tita/admin/Botanic> has quit IRC (Ping timeout: 240 seconds)[22:18:19] <justif> is there a way to do a ssd secure erase from within omnios?[22:18:33] *** slx86 <slx86!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has quit IRC (Ping timeout: 240 seconds)[22:18:33] *** slx87 is now known as slx86[22:20:30] *** slx86 <slx86!~Thunderbi@5ED5B2DA.cm-7-6c.dynamic.ziggo.nl> has quit IRC (Client Quit)[22:24:19] *** Botanic <Botanic!~Botanic@tita/admin/Botanic> has joined #omnios[22:37:52] *** matejz <matejz!~matejz@element.planetq.org> has joined #omnios[22:39:51] *** matejz <matejz!~matejz@element.planetq.org> has quit IRC (Client Quit)[22:42:26] *** ptribble <ptribble!~ptribble@cpc92320-cmbg19-2-0-cust3282.5-4.cable.virginm.net> has quit IRC (Quit: Leaving)[22:49:28] *** synegy34 <synegy34!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has joined #omnios[22:53:02] *** gatekeep <gatekeep!~gatekeep@wls/staff/gatekeep> has quit IRC (Ping timeout: 250 seconds)[22:59:51] *** natkin <natkin!~natkin@cpe-70-117-102-168.austin.res.rr.com> has joined #omnios[23:03:35] *** Kurlon_ <Kurlon_!~Kurlon@bidd-pub-04.gwi.net> has joined #omnios[23:04:08] *** dmip <dmip!~Thunderbi@84.51.125.126> has quit IRC (Ping timeout: 265 seconds)[23:04:11] *** natkin_ <natkin_!~natkin@cpe-70-117-102-168.austin.res.rr.com> has joined #omnios[23:07:20] *** natkin <natkin!~natkin@cpe-70-117-102-168.austin.res.rr.com> has quit IRC (Ping timeout: 250 seconds)[23:07:33] *** Kurlon <Kurlon!~Kurlon@bidd-pub-03.gwi.net> has quit IRC (Ping timeout: 276 seconds)[23:07:43] *** Kurlon_ <Kurlon_!~Kurlon@bidd-pub-04.gwi.net> has quit IRC (Ping timeout: 244 seconds)[23:14:22] *** andy_js <andy_js!~andy@90.219.225.136> has quit IRC (Read error: Connection reset by peer)[23:14:32] *** andy_js <andy_js!~andy@90.219.225.136> has joined #omnios[23:38:35] <justif> what are the odds all my issues were due to iscsi - testing nfs now with them as log devices and seems to be OK[23:39:54] *** Kurlon <Kurlon!~Kurlon@cpe-104-228-216-170.maine.res.rr.com> has joined #omnios[23:41:58] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has quit IRC (Quit: Leaving.)[23:44:02] *** bahamat <bahamat!~bahamat@ip72-199-207-63.sd.sd.cox.net> has joined #omnios[23:58:46] *** synegy34 <synegy34!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has quit IRC (Read error: Network is unreachable)[23:59:19] *** synegy34 <synegy34!~gatekeep@2001:470:8b45:400:7578:bb49:4a1f:bf90> has joined #omnios