20:18:03 <danmcd> ping @Smithx10
20:18:12 <Smithx10> sup
20:19:06 <danmcd> cf. here:   https://hostux.social/@danmcd/109485531514188534
20:19:25 <danmcd> You don't have NVMe-containing pools that you'd jump-backwards for a PI do you?
20:19:56 <danmcd> bahamat and I missed our own flag-day admonishment today. Lucky for us the NVMe drives were slog so no issue detaching them.
20:20:11 <danmcd> (scroll to to the top of the link to see the whole conversation).
20:21:15 <danmcd> I don't think you roll-back PIs beyond maybe "prior release", but if you make the jump from 20220825-or-later to before-20220630, you MUST FIRST boot to one of the four directly mentioned in my link above.
20:21:15 <Smithx10> 1 sec, on a call... I'll take a peak in a few seconds
20:21:37 <danmcd> (no worries)
21:03:09 <blackwood821> Hi, is there any way to stop a Triton NFS volume via CloudAPI or is the only way to do it from the CN global?
21:11:30 <Smithx10> danmcd:  so pretty much all of our CNs are on 20220505T001410Z
21:12:36 <danmcd> Which is well before the fixes.  And jumping forward to something at-or-past 20220825 won't be a problem.  Only jumping FROM that TO an older one would be a problem  (And only for NVMe drives).
21:12:54 <danmcd> "that" == "20220825 or later".
21:13:13 <danmcd> BTW, next week is a Triton bump as well, but you may know that already.
21:13:27 <Smithx10> All the CNs are NVME pools
21:13:36 <Smithx10> except for a few that we use for storage
21:13:41 <danmcd> Oooh, I did remember that right, which was why I pinged you to ask.
21:14:03 <danmcd> Jumping your PI backward on NMVE ones can be hazardous, per above.
21:14:09 <Smithx10> I guess we should just sit tight and wait for a platform that we can move to clean
21:14:32 <danmcd> (Suggest you have one of the middle PIs handy for assignment if you have to jump backward).
21:16:21 <Smithx10> Alright,  I'll import one just in case 
21:16:28 <Smithx10> Thank for the heads up;