16:01:40 [illumos-gate] 17017 zfs: rename get_temporary_prop to zfs_get_temporary_prop -- Toomas Soome 16:07:22 sorry if moving this here is inapropriate, are there clients of the 32 bit userspace other than virtualization? it would seem to me that because it isn't tested as much that defects could creep into 32bit userland unnoticed due to changes in regular 64 bit space that don't cause defects there 16:10:16 forgive me if there is already adequate regression testing to ensure this isn't an actual problem 16:10:29 it is always a problem 16:11:33 I have seen something like no problem in 32bit x86, 64-bit x86, 32-bit sparc but the bug appeared on 64-bit sparc. 16:12:04 tsoome, panorain left the other channel and since 32 bit support involves kernel space i thought it might better here 16:13:49 gcc uses 3 stage bootstrap as a form of validation, could some portion of the userspace be built in 32 bit for the same purpose? maybe not every build but like periodicly 16:14:30 ? most of our userspace is 32-bit 16:14:44 oh, ok 16:14:59 so it's still being vigorously used 16:15:52 yes. and we kind of need to change that;) 16:16:46 there's been a _little_ bit of talk of making most of the binaries 64-bit, but not something that'd happen overnight (and for comapt we'd still need the 32-bit libraries so unbundled stuff that's 32-bit will still run) 16:17:07 i was thinking about ineffiuciencies because of replicated functionality being mapped to memory twice 16:19:46 default should change to 64 bit long before deprecation of 32 bit ideally 17:21:43 well, there's 13 years and 11 days left until the 32-bit userspace starts failing because ld.so.1 will get EOVERFLOW errors on every stat call trying to find libraries to load 17:51:56 thats good:P 17:52:52 somehow (because it'd be too easy :P) i'm guessing we can't just use stat64() or such there... 18:07:03 stat64() uses 64-bit inode & size fields, but still has 32-bit time_t fields - you would need to implement a new variant to get 64-bit time_t fields, like the large time API some Linuxes have provided 18:17:05 https://sourceware.org/glibc/wiki/Y2038ProofnessDesign for example 19:18:25 Howdy I'm using OmniOs and some combination of mashing ^c and ^l ends up bricking my cursor and I can't see what I'm typing. Any ideas what key combination is doing this? 19:19:42 does ^q fix it?;) 19:21:05 or echo ^o^q 19:25:53 ^q did not fix 19:27:13 even like, echo ^v^q ? 19:28:37 the echo commands arent doing anything either 19:29:37 to clarify I am inputting text, the term just isn't displaying my inputs 19:29:58 relogging works, just wondering if anyone had run into this before 19:45:59 Guest39: in Linux I've had it sometimes where the terminal has got messed up and things don't work as expected (display of what's being typed, scrolling etc) in that case the `reset` command at the shell terminal often resets things back to normal - I'm not sure if that's similar to what you're seeing or not and a possible fix 20:44:04 fortunately, you've got nearly 8000 years left to fix https://illumos.org/opensolaris/bugdb/bug.html#!4178551 20:44:04 → OpenSolaris issue 4178551: ctime() has 64-bit year-10000 bug (Defer) 20:48:57 (Defer) 20:52:00 really should just obsolete ctime() before that and convert callers to strftime() instead 21:53:19 alright, I feel sufficiently dumb as I've never had to do this before. How do I partition a disk in 2 on illumos with an EFI label? 21:54:49 every piece of documentation I've looked at starts conflating things with slices. As far as I understand with EFI/GPT, slices are non-overlapping 21:55:08 I just want to carve out ~20 GB from the front and allocate the rest to another partition 21:56:03 format -e should allow you to specify EFI 21:56:23 slices on a GPT disk are just partition entries 21:56:37 yes but then it assumes one single EFI partition, I'm trying to subdivide the disk 21:56:43 though there's some mapping of type (sys, usr, etc) to well known GUID types 21:56:58 you would subdivide the disk 21:57:07 yeah, I found the "fdisk" lets me delete and create just one single partition 21:57:36 I tried the "partition" option, and that won't let me "tag" the partition with an arbitrary name, not that that's important, but it defaults to "usr" 21:58:34 richlowe: step one, draw two circles, step two, draw the rest of the owl? What am I missing here? 21:59:48 what are the "tags"? I've not seen this notion in other UNIXes. FreeBSD has GPT labels, which I assume would be the same thing, but you can arbitrarily name those. You seemingly cannot with the "partition" option from the format command 22:01:43 it's the partition type 22:02:49 in the older SMI disk label format, you had unassigned, boot, root, swap, usr, backup, stand, var, home and a few others 22:03:00 for a GPT disk, those get translated to well known GUIDs 22:04:08 ok, so for a disk that is getting split to go into a zpool, what tag do I assign to both of these? 22:04:16 I assume it basically doesn't matter? 22:05:24 the zpool command uses usr 22:05:31 so that should be fine 22:05:50 you're going to pass the slice in if you don't want it to use the whole disk anyway 22:06:20 you may want to leave the reserved partition that gets created by default as well 22:06:24 gotcha, so I'll basically ignore the p# at the end of the device string 22:06:32 if it's going to be used by illumos 22:06:33 KungFuJesus: sorry, I stepped away. jbk has you covered, there's no separation with EFI/GPT like there used to be 22:07:10 IIRC, the p# ones are for legacy MBR labeled disks 22:07:30 on x86 22:08:11 alright, so, right now when I "label" the GPT disk, it just creates one mega "EFI" partition. I assume the "reserved" one is the ESP partition as it's known on other platforms? 22:08:26 no 22:08:51 it's used by the kernel to store some metadata about the disk in certain circumstances 22:09:17 ah, so something akin to zpool's cache when it "tastes" the drives? 22:09:49 kinda -- basically it wants to try to create a unique identifier for the disk 22:10:06 ah, so that's probably the GUID being stored that ZFS uses? 22:10:10 reserved is used to store fabricated disk ID in case the disk does not provide one. 22:10:34 no that's different :) I think this might predate GPT partitions 22:10:49 I see, I always assumed that was something that was more or less baked into the GPT table in some fashion, but maybe FreeBSD has always simplfied this for me with geom 22:11:21 I mean at the moment, after labeling the disk, the "fdisk" menu just shows me one partition 22:11:33 but yes, if it can't generate a unique id (I think normally it tries to use the WWN of the disk if it has one -- either via scsi inquiry or for SATA it's sometimes buried in the identifying info that gets returned) 22:12:03 oh, "reserved" is at the end 22:12:22 does this have anything to do with GPT's "backup" table? 22:12:25 GPT disk labels to get a unique GUID on them, though if you relabel them, it can generate a new GUID 22:12:33 no 22:13:24 just I'm guessing it's normally just put at the end of the usable LBA range just to try to keep it out of the way 22:13:43 (so the backup GPT label is usually right after it) 22:14:07 ah ok, so this is just a special solaris thing 22:14:12 yes 22:15:06 man, I didn't think it'd be fundamentally this different from BSD given their quasi shared lineage with a distant cousin UFS 22:15:57 i think a lot of the confusion comes with how partitioning was originally done on x86 22:16:20 what are the permission flags? Are the defaults wm fine? 22:16:45 yes, those I think are ignored for GPT 22:18:34 basically on sparc, the legacy (SMI) label supported 8 slices (partitions), each partition had a 1 byte tag (type) which was more of a hint than anything (no place to put a description in UFS, so if you had 4 slices with UFS filesystems on it, it gave you an idea what was what) 22:19:26 and the slices could overlap, so convention was s2 would be a slice that represented the whole disk -- so you could read/write that to backup the disk 22:19:41 when x86 came around, instead of using that on a disk 22:19:51 the first problem is that no BIOS out there would understand it 22:20:01 they only understood MBR partitions 22:20:06 so an issue for your boot disk 22:20:29 so instead, they would take an MBR partition, give it a 'solaris' partition type 22:20:42 and I definitely want to address these by slice, not the p#? Or does it not actually matter? 22:20:44 and then write the SMI label at the part of the partition and subdivide that MBR partition into slices 22:20:56 which is why on x86 you get the p# entries 22:21:09 however once GPT came around 22:21:19 the whole p# wasn't really needed anymore 22:21:54 (for compatability, most things -- not just illumos -- will still write a 'protective' MBR partition table out) 22:22:09 where there's 1 MBR partition (of type UEFI) 22:22:15 but that can pretty much be ignored 22:22:22 I mean to be fair, the 4th based loaders didn't need to make slices overlappable. Making 2 the whole disk was also seemingly a bizarre choice 22:22:39 so you want to use the slice devices 22:22:55 as those will map to the GPT partition entries 22:23:20 ok, so instead of the protective MBRs, which are probably using a layer of glue somewhere 22:26:01 I don't know if there'd be any unexpected issues, but it seems like we could probably stop creating (at least by default) the p# entries on GPT disks since they are kinda confusing 22:29:40 you mean device nodes? that is not bad idea 22:40:10 now my understanding of l2arc_noprefetch, setting this to 0 with mdb doesn't do anything until you reimport the pool? 22:40:37 or, would simple setting this to 0 be enough for prefetched things to land in l2arc from an already imported pool? 22:40:43 simply* 22:41:16 (I did set it in /etc/system, I'm just trying to avoid a reboot) 22:46:37 i think it'll take effect immediately (though won't impact any l2arc data that's already been prefetched -- i.e. changing it won't evict anything exiting) 22:48:42 ok, but it'll probably hit the cache the second time around after it's flushed out. Awesome 23:07:10 you would probably like this one too: https://github.com/openzfs/zfs/commit/043c6ee3b6bfb55f8d36e1f048ff13128c279fb8 23:07:39 I figured I did see l2arc_noprefetch somewhere... 23:56:02 KungFuJesus: You basically never want the fdisk(8) command, or the "fdisk" menu in format(8), unless you're looking to create an old fashioned vtoc-style partition (the SOLARIS2 type) inside an old fashioned MBR-only disk 23:56:15 and yes, always the slice (s*) devices 23:56:39 unless you need the "whole disk" device, which is p0