nikolam: /Joyent_Dev/public/SmartDataCenter/release-20230209-20230210T151601Z-gd283f34/md5sums.txt

nikolam: Most of the build artifacts aren't really expected to be consumed directly.

The main reason the release directory has them is because they're there for the dev builds where we need to be able to fetch them independent from updates.tritondatacenter.com.

There's not really any reason that a non-developer would need to download say, build.spec.merged for any triton build.

The files that, as a consumer, you'd want access to are linked from the main page.

I were thinking of installing Triton locally on low spec machine headnode and try using it. Similar to how Smartos have it's index.html page. It's called Coal as I understand, if is downloading to be installed, then easy getting md5sums etc. would be also nice.

Well, coal is the vmware image.

If you're installing it on hardware then you want the USB or ISO image, depending on what boot media is available to you.

CoaL isn't like a "mini" version. It's literally just a vmware disk image with the USB image written into it.

And you don't even need the coal image, you can use the iso image with vmware.

Yeah yeah USB. Sorry, my mistake. I were comparing their use cases. It's late here. So yes, runing Triton on hardware

The coal image isn't even tuned for a smaller size. It's something like 300% overprovisioned on ram and 3000% overprovisioned on disk. But those are really resource caps that don't usually get hit.

ballooning

yeah, i dont like that in my vmware vm's

just use what i say...

snapshots/backing leave me alone, vmware17 is even more aggressive...and im sure esxi...

transparent_hugepage on linsux goes crazy

going all the way back to vmware12/player/workstation

is there any change in carp support on smartos VMs? ...when I've checked the last time it's not possibile to have a virtual mac needed by carp ...is this limitation still there?

xmerlin: There hasn't been any significant changes there...but did you allow_mac_spoofing?

it doesn't work ...there is also an issue on github ...it's related to viona change if I remember correctly

no carp / vrrp can work on smartos without this change ...if I remember correctly rmystacc pointed a patch never merged in the smartos/illumos codebase

Anyway to find out when a disk in a zpool went into the "removed" state?

what about zpool history?

or does that only report which zfs commands where used on the pool?

think that only show thes commands

zpool history -i ?

lol

so much info !

:P

Thanks neuroserve

did you find something useful in the output?

2023-02-10.16:23:55 [txg:13673861] vdev attach spare in vdev=/dev/dsk/c3t5000CCA270AFCA31d0s0 for vdev=/dev/dsk/c3t5000CCA270ADCD71d0s0

:)

not bad