02:35:18 <Dotz0cat> I now got to get my wifi working. I got to get my wifi arn0 up in ifconfig. I have plumbed it. and I have tried running ifconfig arn0 up. But it still shows down in dladm. Tommorow's problem I guess.
15:02:17 <gitomat> [illumos-gate] 15504 ZFS/libshare is too verbose when services are not present -- Andy Fiddaman <illumos⊙fn>
15:47:52 <gitomat> [illumos-gate] 15500 tgtmap(9) tgt_privp doesn't work as advertised -- Hans Rosenfeld <rosenfeld⊙gho>
16:17:58 <neirac> is it correct to not see vioblk interrupts ? https://termbin.com/wi1m. 
17:02:01 <jbk> do you have any vioblk devices?
17:03:23 <jbk> I think you should see 'vioblk_int_handler' if any vioblk devices have attached
17:09:22 <neirac> https://termbin.com/nml4 that's prtconf -d I thought having vioscsi meant having vioblk
17:09:59 <jbk> no, they are two different types of devices
17:10:53 <jbk> vioblk uses its own (simplified) set of commands (read, write, etc) for a storage device
17:11:28 <jbk> while vioscsi uses the SCSI command set (far, far more complex)
17:20:07 <neirac> jbk oh ok, thank you!
17:21:32 <neirac> jbk is it possible to use fixed interrupts for vioscsi ? https://termbin.com/16u1
17:38:35 <jclulow> neirac: MSI-X is really what you want.  Why do you need fixed interrupts?
17:44:06 <neirac> jclulow I was reading this ticket https://www.illumos.org/issues/12015 , trying to find out why trying smartos in oracle cloud fails when writing to the disk(my assumption) as it not possible to create a zpool
17:44:07 <fenix> → BUG 12015: vioif with MSI-X not working on Google Compute Engine (Closed)
17:44:26 <jclulow> I would not assume it is related 
17:44:45 <jclulow> GCE has a totally custom hypervisor thing and it has specific quirks
17:52:00 <neirac> jclulow ohh, ok. the issue is totally different then. I'll try to troubleshoot more time the disk
17:52:32 <jclulow> Yeah, I had to do a fair amount of interactive debugging to figure that out
17:52:53 <jclulow> Which at least was possible because GCE provides a decent serial console!
17:53:02 <jclulow> Hopefully Oracle cloud does too 
17:53:46 <neirac> jclulow oh yes, I'm in a serial console, I boot through ipxe
17:53:53 <jclulow> Great
17:54:23 <neirac> I assume this should work on any disk prtvtoc: /dev/rdsk/c1t0d1s0, but I'm getting this  Unable to read Disk geometry errno = 0x5
17:57:14 <jclulow> It might not work if it hasn't ever been labelled?  I can't remember 
17:57:34 <jclulow> Try to give it an EFI label with format -e
18:04:27 <sommerfeld> neirac: I'm pretty sure that's what you get if there is no label.
18:32:15 <tsoome> fastest way to create label is zpool create ..; zpool destroy.
18:35:12 <neirac> tsoome I tried zpool labelclear but failed : failed to open /dev/dsk/c1t0d1s0: I/O error
18:36:59 <tsoome> not labelclear, create.
18:37:37 <tsoome> we create disk label with wholedisk setup;)
18:38:02 <neirac> tsoome zpool create  c1t0d1 cannot label 'c1t0d1': try using fdisk(8) and then provide a specific slice
18:41:37 <tsoome> wot. hm what is device tree for it?
18:41:43 <tsoome> device path*
18:43:38 <tsoome> ls -l /dev/dsk/c1t0d1s0 would show you link to /devices tree
18:43:55 <tsoome> or format will show it in disk list
18:57:08 <neirac> tsoome lrwxrwxrwx   1 root     root          57 Mar 21 13:52 /dev/dsk/c1t0d1s0 -> ../../devices/pci@0,0/pci108e,8@4/iport@iport0/disk@0,1:a
18:57:27 <tsoome> anyhow, for EFI label, you would need to create 100% EFI partition in fdisk (either run directly or format -> fdisk)
18:58:42 <tsoome> iport? sas?
19:16:19 <tsoome> this is vioscsi, I presume.
19:16:36 <neirac> tsoome yes, is vioscsi
19:18:13 <tsoome> I'm on thin ice there, but vioscsi does not provide cmlb_tg_ops_t -- I'm not sure if it is supposed to or if there is something else stacked on vioscsi
19:18:57 <tsoome> cmlb_tg_ops_t will provide callbacks for disk label (cmlb) from block device 
19:22:20 * nomad checks notes
19:22:39 <nomad> looks like I've used 'fdisk -B' successfully in the past to add/replace labels on drives before adding them to a zpool.
19:24:28 <jclulow> err
19:24:34 <jclulow> fdisk not required?
19:24:47 <jclulow> format -e will create an EFI label if you ask it
19:25:08 <nomad> I honestly don't remember why that was a necessary thing, just in my notes that I did it.
19:25:15 <jclulow> tsoome: sd provides cmlb
19:25:22 <jclulow> it's SCSI, so vioscsi is just the HBA
19:25:28 <jclulow> sd is the disk target driver that would sit on top
19:25:47 <jclulow> Because it's all not working right, I would use format -e on the disk and try to create the label
19:25:54 <jclulow> and then observe why that isn't working
19:26:19 <jclulow> Some sytem call like open(), or ioctl(), or even some read()/write() will be failing
19:26:23 <jclulow> *system
19:26:23 <tsoome> format has its own quirks.
19:26:31 <jclulow> It's baroque but it's fine
19:26:52 <jclulow> It should work here, for this, at least, and if it doesn't, there is a bug
19:27:19 <tsoome> we have added support for some devices in format in past
19:27:41 <neirac> ok, I'll try format now 
19:28:44 <jclulow> vioscsi should just be sd disks, though, not a new type
19:30:14 <neirac> format failed https://termbin.com/s4zf
19:31:03 <jclulow> oof
19:31:06 <jclulow> Current Disk is unformatted.
19:31:10 <jclulow> that is ... not ideal haha
19:31:24 <jclulow> You should figure out why we think that
19:31:44 <jclulow> this part actually seems to work at least: c1t0d1 <ORACLE-BlockVolume-1.0-46.58GB>
19:32:02 <jclulow> so we're getting some of the SCSI pages that identify the disk vendor/model and capacity
19:32:36 <jclulow> FWIW, you should not have to use the "format" command there
19:32:45 <jclulow> Especially not for a virtual disk
19:33:05 <neirac> jclulow at least I know what to check now
19:33:10 <jclulow> Yup!
19:33:37 <jclulow> That "is unformatted" message will come from something in format, which will have been a decision based on some ioctl or whatevr
19:33:49 <jclulow> and ... you'll be able to trace that back to something sd got from the disk basically
19:34:30 <jclulow> at least it looks merely like a SCSI thing, and not some interrupts bullshit
19:34:34 <jclulow> interrupts are the worst hhaa
19:34:36 <jclulow> *haha
21:28:41 <neirac> jclulow thanks!!
21:30:56 <jclulow> You're welcome!
22:32:16 <gitomat> [illumos-gate] 15506 zfs and zpool tests can fail because of core size limit -- Toomas Soome <tsoome⊙mc>
22:35:43 <neirac> I just compiled format with developer menu but I don't know how to translate the info to be good or bad https://termbin.com/asyy