03:08:30 hrm.. if you disable the loading of a module from the bootloader, can you later manually load the module? 03:30:09 [illumos-gate] 16150 scsi_vhci probing doesn't respect device block size -- Jason King 09:18:27 jbk I haven't tried, but it looks like you should be able to unset the DN_DRIVER_REMOVED bit in devnamesp[major].dn_flags 11:23:24 Hello! I am completely new with Illumos, started to experiment with OpenIndiana and OmniOS just recently. I started to think about trying myself out in open-source contribution. I took a look at the bite-size bug reports, and also found a contribution guide on the illumos site, but it described some complicated review and quality check process. I 11:23:25 was thinking about selecting this issue as first step https://www.illumos.org/issues/16193 but as far as I understand, this requires only a change in the specific manpage, and not a code change. If someone knows, could help me please, whether I am allowed to try to fix this ticket or not, and if yes, then in this case how the contribution process 11:23:25 looks like? Because as far as I understand the more complex review process is for code changes. Thank you in advance! 11:23:27 → BUG 16193: loader(7) doesn't correctly explain how to drop into kmdb at boot (New) 14:34:29 andyf: i will give that a try (will be quicker than a rebuild :P) 16:03:02 oh bmc hardware, why do you have to be so terrible... 16:37:03 lgh127001: you're not here, but you might check the logs. 16:38:58 lgh127001: anyone is welcome to send in proposed changes. the amount of testing required before a change is accepted depends on the type and scope of change, but even manpage changes are "code" of a sort (written in mandoc). 16:40:20 lgh127001: the first thing I'd work on would be ensuring that you can check out illumos-gate on an illumos system and run "nightly" to build the gate. 16:53:38 one of these days, i need to figure out why dumping to a zvol is _significantly_ slower than a raw device (i'd imagine some overhead, but 40-60 mins to save a crash dump feels excessive) 17:05:49 [illumos-gate] 16163 zfs scrub should pause scan when memory is low -- Bill Sommerfeld 17:31:45 lgh127001: welcome back. 17:31:57 Yes sorry I'm logged off because have to carry this device with me so this is easier this way, but I'm checking the logs. Thank you, then I will try a checkout and build first. What distribution you think would be the most suitable for beginning (meaning the most documentation available, the less chance of overlooking/messing up something, maybe 17:31:57 one has etter tooling than the other etc)? 17:32:20 not "etter" but "better" sorry 17:36:14 depends on your goals for illumos. either omnios or openindiana should work for building. Tooling should generally similar. As for which, opinions vary. Openindiana if you want something that's like a traditional workstation. Omnios is probably in better shape if you want to host virtual machines on illumos. 17:57:52 [illumos-gate] 14455 Convert ld(1) to mdoc -- Andy Fiddaman 20:19:32 jbk: what is the pool topology under the zvol? 20:28:31 2 way mirror on SSDs 20:29:37 how big is the dump? 20:31:54 it varies unfortunately anywhere from 10-100gb.. i'd obviously expect a large dump to take longer, but it still seems way longer than it should be 20:32:04 just... that's a challenging context to debug 20:36:00 Perhaps something like fio could also show the difference? 20:47:35 I would probably start by adding just a little more information to the dump status output 20:47:49 right now I think it just shows how long it's been running and what the % of completion is? 20:48:19 hrtime is available, I expect it would be pretty easy to measure min/max/avg/etc latency of I/Os for example 20:48:25 yeah 20:49:06 If the I/O issue size is variable it might be a little more complex to reason about 20:49:22 (I can't remember if it's always PAGESIZE or if it gangs things together sometimes) 20:50:24 i was just reminded of it since I had to force a dump for a vendor so they can figure out why the latest version of their driver hangs enumerating devices during boot 20:50:46 andyf: btw, that worked 20:51:19 well enumerating devices, including during boot (or I guess more specifically during attach) 21:09:53 There is also METRICS.cxv which I haven't looked at in a long time, but may be useful still if you have that enabled bjk. 21:09:56 *jbk 21:18:00 [illumos-gate] 16121 want viorand -- Toomas Soome 22:04:20 126 MB/s if i'm reading that right 23:04:09 i know there is no official illumos dev space @ fosdem, but is there an unofficial one somewhere?