• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

The Geek Diary

HowTos | Basics | Concepts

  • Solaris
    • Solaris 11
    • SVM
    • ZFS
    • Zones
    • LDOMs
    • Hardware
  • Linux
    • CentOS/RHEL 7
    • RHCSA notes
    • SuSE Linux Enterprise
    • Linux Services
  • VCS
    • VxVM
  • Interview Questions
  • oracle
    • ASM
    • mysql
    • RAC
    • oracle 12c
    • Data Guard
  • DevOps
    • Docker
    • Shell Scripting
  • Hadoop
    • Hortonworks HDP
      • HDPCA
    • Cloudera
      • CCA 131

How to enable the automatic extension for a thin LVM volume

By admin

By default, the automatic extension is set to ‘100‘

# grep thin_pool_autoextend_threshold /etc/lvm/lvm.conf
# Configuration option activation/thin_pool_autoextend_threshold.
# thin_pool_autoextend_threshold = 70
  thin_pool_autoextend_threshold = 100

These settings imply the function has been disabled. From the /etc/lvm/lvm.conf configuration file:

# ‘thin_pool_autoextend_threshold’ and ‘thin_pool_autoextend_percent’ define
# how to handle automatic pool extension. The former defines when the
# pool should be extended: when its space usage exceeds this many
# percent. The latter defines how much extra space should be allocated for
# the pool, in percent of its current size.
#
# For example, if you set thin_pool_autoextend_threshold to 70 and
# thin_pool_autoextend_percent to 20, whenever a pool exceeds 70% usage,
# it will be extended by another 20%. For a 1G pool, using up 700M will
# trigger a resize to 1.2G. When the usage exceeds 840M, the pool will
# be extended to 1.44G, and so on.
#
# Setting thin_pool_autoextend_threshold to 100 disables automatic
# extensions. The minimum value is 50 (A setting below 50 will be treated
# as 50).

To enable the automatic extension, change both the ‘thin_pool_autoextend_percent‘ and ‘thin_pool_autoextend_threshold‘ settings:

thin_pool_autoextend_threshold = 70
thin_pool_autoextend_percent   = 20

Which means whenever a pool exceeds 70% usage, it will be extended by another 20%. For a 1G pool, using 700M will trigger a resize to 1.2G. When the usage exceeds 840M, the pool will be extended to 1.44G, and so on.

Filed Under: CentOS/RHEL 6, CentOS/RHEL 7, Linux

Some more articles you might also be interested in …

  1. Getting “parsing errors” When Running ‘yum repolist’
  2. How to make alias command work in bash script or bashrc file
  3. How to configure and Manage Network Connections using nmcli
  4. How to send Audit Logs to Remote Rsyslog Server in CentOS/RHEL 6,7
  5. How to Change Timezone from CST To EST in CentOS/RHEL 7 Server
  6. The System Activity Reporter (sar) Command in Linux
  7. CentOS / RHEL 7 : Beginners guide to firewalld
  8. Troubleshooting kdump Issues in CentOS/RHEL
  9. What’s different between /bin/false and /sbin/nologin as nologin user’s shell
  10. “docker dead but subsys locked” – error while starting docker

You May Also Like

Primary Sidebar

Recent Posts

  • How to change the default IP address of docker bridge
  • “su: Authentication failure” – in Docker
  • How to Pause and Resume Docker Containers
  • How to find docker storage device and its size (device mapper storage driver)
  • Understanding “docker stats” Command Output
  • Archives
  • Contact Us
  • Copyright

© 2019 · The Geek Diary