Adding a Cron Job for Automatic TRIM in Proxmox VE
Adding a Cron Job for Automatic TRIM in Proxmox VE
Check the status
|
|
Start the service
|
|
Check the next cleanup time
|
|
Done
|
|
|
|
|
|
Done
The proxmox ve I installed earlier on the DIY E3 server used a 120G SSD. Back then, being young and naive, I also carved a 30g data partition out of the pve logical volume. Now I want to use local for glusterfs, so I wanted to merge the space in data into root.
data partitionpve webui; for what you do need, copy it out first. My data is mounted at /mnt/data:
|
|
data logical volume:
|
|
|
|
|
|
vg space with sudo vgdisplay:
|
|
30.39 Gib of space. Now merge it into pve-root:sudo lvresize -l +100%FREE /dev/pve/root:
|
|
It becomes 103.10 GiB.
A few days ago I deployed a two-node proxmox ve cluster. It worked fine at first, but after a day, when I logged in to the dell r720 host over ssh, I found the shell responding very slowly, and going into the linux container on it was even worse — every time I typed a command, zsh would freeze for quite a while.
When I first set up the glusterfs cluster I was in a hurry and used the network addresses of the pve hosts directly. After a few days I noticed that when volume replication ran it was saturating the pve hosts’ own network channel. The dell r720 happened to have four NICs and the e3 host had two, so I took one from each and dedicated it as the gluster bind address.
The following code:
|
|
At runtime it reports: Nest can't resolve dependencies of the SiteRbacService, and the log shows that @InjectRepository(RbacEntity) public readonly repository: Repository<RbacEntity> was not injected.
First, find the id of the disk you want to mount:
|
|
The output looks similar to this:
|
|
For example, to mount /dev/disk/by-id/wwn-0x5000000000000 for a VM whose ID is 103, run the following: