[SOLVED] Where do I set below threshold?

[LooneyTunes]

Hi,

I have recently begun to see warnings like this when taking snapshots. I spent time before trying to figure out what and where this needs to go, but did not find that. I pruned some old backups etc, but did not seem to have any effect. I get I need to set protection below, question is where and possibly also how? Thanks

snapshotting 'drive-scsi0' (local-lvm:vm-104-disk-0)
  WARNING: You have not turned on protection against thin pools running out of space.
  WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full.
  Logical volume "snap_vm-104-disk-0_OS_ready" created.
  WARNING: Sum of all thin volume sizes (352.00 GiB) exceeds the size of thin pool pve/data and the amount of free space in volume group (<16.00 GiB).
TASK OK

 

[datschlatscher]

The suggested setting does not really resolve this warning, because (as far as I know) it will always be printed when the sum of the size of all the disks you created in the thin-pool, exceeds the size of the thin-pool. However, as long as you monitor your thin-pool to not run out of space, you can safely ignore the warning.

Here is another forum thread discussing this warning in some more detail.

There is an open Github issue on the LVM repository for this, but it seems it hasn't been picked up by any developer yet.

 

[LooneyTunes]

The suggested setting does not really resolve this warning, because (as far as I know) it will always be printed when the sum of the size of all the disks you created in the thin-pool, exceeds the size of the thin-pool. However, as long as you monitor your thin-pool to not run out of space, you can safely ignore the warning.

Here is another forum thread discussing this warning in some more detail.

There is an open Github issue on the LVM repository for this, but it seems it hasn't been picked up by any developer yet.

Thank you! Then I'll just monitor it for now, it'll work fine for now

 

[tuxick]

I think "SOLVED" is not really the correct term for this thread.