I have upgraded to Ventura and while the modifications are not bad, Apple managed to wreck something that was working very well on previous macOS versions and also on countless linux servers around the world. Yes, I am talking about Samba.

I had an issue a couple of days ago in which I had the /docker filesystem full and unable to pinpoint exactly which docker container is using it.
Fortunately docker comes with powerful utilities to help you out with this.
Follow what comes if curious.

How to check how docker is using the system space:

The following commands even if they are close they provide different output. the -v option will give you way more details
docker system df -v
docker system df

The following pool is normal, not mirror, on one disk

18:02:00 root@eeny:~# zpool status
  pool: tm
 state: ONLINE
  scan: resilvered 3.11T in 16:27:30 with 0 errors on Fri Apr  1 13:07:34 2022
config:

	NAME        STATE     READ WRITE CKSUM
	tm          ONLINE       0     0     0
	  sdb1      ONLINE       0     0     0

I have another disk, same size and I would like to convert this pool into a mirror one

Fount this problem today and must share it with you.

01:09:18 root@eeny:~# zpool import tm
cannot import 'whatever': no such pool available

Oops, got scared a bit :)
You should not because what follows may help you.
That is assuming the disk with that pool is attached, available and not damaged :D

Got this error today when I started a docker container with the latest available image from docker hub (2022.02.1):

I attached a disk one day and was impossible to create datastore on it via web interface.
Well, did not thought much about it and went directly on command line, via ssh and if you are curious, please follow.

1. Get the partition table information:

[root@eeny:~] partedUtil "getptbl" /vmfs/devices/disks/mpx.vmhba34\:C0\:T0\:L0 
gpt
364801 255 63 5860533168

2. Get the end sector value:

NOTE: start sector value is 2048

You are here because you cannot find glances via apt, right?
I got into the same issue but differently. I removed glances because it was giving the following error:
glances AttributeError: 'ThreadScanner' object has no attribute 'isAlive'.

And when I attempted to reinstall it back, SURPRISE! Not available :D

Actually you cannot resize the OS partition on an existing ESXi installation but you can backup the configuration, reinstall with the right options and restore back the configuration.
You could probably also migrate during the installation process but I haven't tested that yet.

So, without much typing here we go.

With SSD arriving more and more in our lives it is natural to find it on linux servers too.
Not working with SSD in this area much, haven't found much interest of finding ssd related things in Linux so far.

So, nowadays one can wonder wondering: how would I know if my disks in Linux are SSD or not?
A valid response would be: close the system, open it up and see what disk you have there :)))

But what if this is a linux server far far away? You need to be able to find out these things from OS level.

So, we need to increase the following OCFS2 partition which sits on a drbd volume (which sits on lvm2 volume).
The grow steps have to be taken in the right order: lvm2, drbd and ocfs2.

This tutorial comes in text (below) and in youtube video (also below).
Enjoy ;)

1. Increase LVM partition on ALL NODES

Command: lvresize -L+20G /dev/dockervg/data