15:23:56 <nikolam> Can someone check, I made LX Uvuntu 22.04 VM , updated downloaded https://download.nextcloud.com/server/releases/latest.tar.bz2 and trying to unpack it with tar xvzf latest.tar.bz2 . On "Native Ubuntu install on hardware it uncompress it fine. in LX zone it says: 
15:24:39 <nikolam> ar (child): bzip2: Cannot exec: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now
15:25:08 <jperkin> sounds like you don't have bzip2 installed on the latter
15:31:58 <nikolam> Ok, I am stupid, sorry. 
18:59:48 <pjustice> Fault manager question.  I have a machine that keeps reporting a fault in fan 4.  I mark it repaired, it runs for hours or days, faults again.  I replaced the fan.  Ran for five or six days, faulted again.  So now I want to ensure that I replaced the _right_ fan.  Is the human readable FRU name in the `faulty` report drawn from the baseboard?  (If so I would expect it the match the labels on the fan 
18:59:54 <pjustice> connectors.)  ...
18:59:57 <pjustice> ... Is there a way to inform fmd that a given FRU should be ignored?  At this point I feel like the fan isn't actually failing, and one option might be to live with five instead of six.
19:09:20 <jbk> unfortunately it depends
19:10:45 <jbk> if the system has a BMC/RMM/iLO/Drac/.... there's a decent chance it's getting the info via IPMI, in which case it'll like match what shows up in the BMC, which is _probably_ the same thing as what's labeled on the baseboard
19:11:03 <jbk> but there's no guarantee unfortunately
19:13:24 <pjustice> It's a SuperMicro SYS-120C-TR, if that adds any useful info.
19:19:18 <pjustice> Also, if it can't get info via IPMI, what does it use?
20:36:04 <jbk> hrm..
20:36:17 <jbk> gmake clean doesn't appear to clear out old openssl3 versions under illumos-extra
20:37:00 <jbk> my build zone ran out of space, and the openssl3 directory alone was consuming 11GB
20:37:17 <pjustice> neat