{
    "mode": "man",
    "parameter": "lvmcache",
    "section": "7",
    "url": "https://www.chedong.com/phpMan.php/man/lvmcache/7/json",
    "generated": "2026-11-14T01:35:47Z",
    "sections": {
        "NAME": {
            "content": "lvmcache — LVM caching\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "lvm(8) includes two kinds of caching that can be used to improve the performance of a Logical\nVolume  (LV).  When  caching,  varying  subsets  of  an LV's data are temporarily stored on a\nsmaller, faster device (e.g. an SSD) to improve the performance of the LV.\n\nTo do this with lvm, a new special LV is first created from the faster device. This  LV  will\nhold  the cache. Then, the new fast LV is attached to the main LV by way of an lvconvert com‐\nmand. lvconvert inserts one of the device mapper caching targets into the main LV's i/o path.\nThe device mapper target combines the main LV and fast LV into a  hybrid  device  that  looks\nlike  the  main  LV, but has better performance. While the main LV is being used, portions of\nits data will be temporarily and transparently stored on the special fast LV.\n\nThe two kinds of caching are:\n\n• A read and write hot-spot cache, using the dm-cache kernel module.  This cache  tracks  ac‐\ncess  patterns and adjusts its content deliberately so that commonly used parts of the main\nLV are likely to be found on the fast storage. LVM refers to this using the LV type cache.\n\n• A write cache, using the dm-writecache kernel module.  This cache can be used with  SSD  or\nPMEM  devices  to  speed  up  all  writes to the main LV. Data read from the main LV is not\nstored in the cache, only newly written data.  LVM refers to this using the LV type  write‐\ncache.\n",
            "subsections": []
        },
        "USAGE": {
            "content": "",
            "subsections": [
                {
                    "name": "1. Identify main LV that needs caching",
                    "content": "The  main LV may already exist, and is located on larger, slower devices.  A main LV would be\ncreated with a command like:\n\n# lvcreate -n main -L Size vg /dev/slowhhd\n"
                },
                {
                    "name": "2. Identify fast LV to use as the cache",
                    "content": "A fast LV is created using one or more fast devices, like an SSD.  This special  LV  will  be\nused to hold the cache:\n\n# lvcreate -n fast -L Size vg /dev/fastssd\n\n# lvs -a\nLV   Attr       Type   Devices\nfast -wi------- linear /dev/fastssd\nmain -wi------- linear /dev/slowhhd\n"
                },
                {
                    "name": "3. Start caching the main LV",
                    "content": "To  start  caching  the main LV, convert the main LV to the desired caching type, and specify\nthe fast LV to use as the cache:\n\nusing dm-cache (with cachepool):\n\n# lvconvert --type cache --cachepool fast vg/main\n\nusing dm-cache (with cachevol):\n\n# lvconvert --type cache --cachevol fast vg/main\n\nusing dm-writecache (with cachevol):\n\n# lvconvert --type writecache --cachevol fast vg/main\n\nFor more alteratives see:\ndm-cache command shortcut\ndm-cache with separate data and metadata LVs\n"
                },
                {
                    "name": "4. Display LVs",
                    "content": "Once the fast LV has been attached to the main LV, lvm reports the main  LV  type  as  either\ncache  or  writecache depending on the type used.  While attached, the fast LV is hidden, and\nrenamed with a cvol or cpool suffix.  It is displayed by lvs -a.  The corig or wcorig  LV\nrepresents the original LV without the cache.\n\nusing dm-cache (with cachepool):\n\n# lvs -ao+devices\nLV                 Pool         Type       Devices\nmain               [fastcpool] cache      maincorig(0)\n[fastcpool]                    cache-pool fastpoolcdata(0)\n[fastcpoolcdata]              linear     /dev/fastssd\n[fastcpoolcmeta]              linear     /dev/fastssd\n[maincorig]                    linear     /dev/slowhhd\n\nusing dm-cache (with cachevol):\n\n# lvs -ao+devices\n\nLV           Pool        Type   Devices\nmain         [fastcvol] cache  maincorig(0)\n[fastcvol]              linear /dev/fastssd\n[maincorig]             linear /dev/slowhhd\n\nusing dm-writecache (with cachevol):\n\n# lvs -ao+devices\n\nLV            Pool        Type       Devices\nmain          [fastcvol] writecache mainwcorig(0)\n[fastcvol]               linear     /dev/fastssd\n[mainwcorig]             linear     /dev/slowhhd\n"
                },
                {
                    "name": "5. Use the main LV",
                    "content": "Use the LV until the cache is no longer wanted, or needs to be changed.\n"
                },
                {
                    "name": "6. Stop caching",
                    "content": "To stop caching the main LV and also remove unneeded cache pool, use the --uncache:\n\n# lvconvert --uncache vg/main\n\n# lvs -a\nLV   VG Attr       Type   Devices\nmain vg -wi------- linear /dev/slowhhd\n\nTo stop caching the main LV, separate the fast LV from the main LV.  This changes the type of\nthe main LV back to what it was before the cache was attached.\n\n# lvconvert --splitcache vg/main\n\n# lvs -a\nLV   VG Attr       Type   Devices\nfast vg -wi------- linear /dev/fastssd\nmain vg -wi------- linear /dev/slowhhd\n"
                },
                {
                    "name": "7. Create a new LV with caching",
                    "content": "A  new  LV  can  be created with caching attached at the time of creation using the following\ncommand:\n\n# lvcreate --type cache|writecache -n Name -L Size\n--cachedevice /dev/fastssd vg /dev/slowhhd\n\nThe main LV is created with the specified Name and Size from the slowhhd.  A hidden fast  LV\nis  created  on the fastssd and is then attached to the new main LV.  If the fastssd is un‐\nused, the entire disk will be used as the cache unless the  --cachesize  option  is  used  to\nspecify  a  size  for  the fast LV.  The --cachedevice option can be repeated to use multiple\ndisks for the fast LV.\n"
                }
            ]
        },
        "OPTIONS": {
            "content": "",
            "subsections": [
                {
                    "name": "option args",
                    "content": "--cachepool CachePoolLV|LV\n\nPass this option a cachepool LV or a standard LV.  When using a cache pool, lvm places  cache\ndata  and  cache  metadata  on  different LVs.  The two LVs together are called a cache pool.\nThis has a bit better performance for dm-cache and permits  specific  placement  and  segment\ntype  selection for data and metadata volumes.  A cache pool is represented as a special type\nof LV that cannot be used directly.  If a standard LV is passed with this  option,  lvm  will\nfirst  convert  it to a cache pool by combining it with another LV to use for metadata.  This\noption can be used with dm-cache.\n\n--cachevol LV\n\nPass this option a fast LV that should be used to hold the cache.   With  a  cachevol,  cache\ndata and metadata are stored in different parts of the same fast LV.  This option can be used\nwith dm-writecache or dm-cache.\n\n--cachedevice PV\n\nThis  option  can be used in place of --cachevol, in which case a cachevol LV will be created\nusing the specified device.  This option can be repeated to create a cachevol using  multiple\ndevices,  or a tag name can be specified in which case the cachevol will be created using any\nof the devices with the given tag.  If a named cache device is unused, the entire device will\nbe used to create the cachevol.  To create a cachevol of a specific size from the  cache  de‐\nvices, include the --cachesize option.\n"
                },
                {
                    "name": "dm-cache block size",
                    "content": "A cache pool will have a logical block size of 4096 bytes if it is created on a device with a\nlogical block size of 4096 bytes.\n\nIf  a  main LV has logical block size 512 (with an existing xfs file system using that size),\nthen it cannot use a cache pool with a 4096 logical block size.  If the  cache  pool  is  at‐\ntached, the main LV will likely fail to mount.\n\nTo avoid this problem, use a mkfs option to specify a 4096 block size for the file system, or\nattach the cache pool before running mkfs.\n"
                },
                {
                    "name": "dm-writecache block size",
                    "content": "The dm-writecache block size can be 4096 bytes (the default), or 512 bytes.  The default 4096\nhas  better  performance  and  should be used except when 512 is necessary for compatibility.\nThe dm-writecache block size  is  specified  with  --cachesettings  blocksize=4096|512  when\ncaching is started.\n\nWhen a file system like xfs already exists on the main LV prior to caching, and the file sys‐\ntem  is using a block size of 512, then the writecache block size should be set to 512.  (The\nfile system will likely fail to mount if writecache block size of 4096 is used in this case.)\n\nCheck the xfs sector size while the fs is mounted:\n\n# xfsinfo /dev/vg/main\nLook for sectsz=512 or sectsz=4096\n\nThe writecache block size should be chosen to match the xfs sectsz value.\n\nIt is also possible to specify a sector size of 4096 to mkfs.xfs when creating the file  sys‐\ntem.  In this case the writecache block size of 4096 can be used.\n\nThe writecache block size is displayed by the command:\nlvs -o writecacheblocksize VG/LV\n"
                },
                {
                    "name": "dm-writecache memory usage",
                    "content": "The  amount  of  main  system memory used by dm-writecache can be a factor when selecting the\nwritecache cachevol size and the writecache block size.\n\n• writecache block size 4096: each 100 GiB of writecache cachevol uses slighly over 2 GiB  of\nsystem memory.\n\n• writecache block size 512: each 100 GiB of writecache cachevol uses a little over 16 GiB of\nsystem memory.\n"
                },
                {
                    "name": "dm-writecache settings",
                    "content": "To specify dm-writecache tunable settings on the command line, use:\n--cachesettings 'option=N' or\n--cachesettings 'option1=N option2=N ...'\n\nFor example, --cachesettings 'highwatermark=90 writebackjobs=4'.\n\nTo include settings when caching is started, run:\n\n# lvconvert --type writecache --cachevol fast \\\n--cachesettings 'option=N' vg/main\n\nTo change settings for an existing writecache, run:\n\n# lvchange --cachesettings 'option=N' vg/main\n\nTo clear all settings that have been applied, run:\n\n# lvchange --cachesettings '' vg/main\n\nTo view the settings that are applied to a writecache LV, run:\n\n# lvs -o cachesettings vg/main\n\nTunable settings are:\n\nhighwatermark = <percent>\nStart writeback when the writecache usage reaches this percent (0-100).\n\nlowwatermark = <percent>\nStop writeback when the writecache usage reaches this percent (0-100).\n\nwritebackjobs = <count>\nLimit  the  number  of blocks that are in flight during writeback.  Setting this value\nreduces writeback throughput, but it may improve latency of read requests.\n\nautocommitblocks = <count>\nWhen the application writes this amount of blocks without issuing the  FLUSH  request,\nthe blocks are automatically commited.\n\nautocommittime = <milliseconds>\nThe  data  is  automatically  commited if this time passes and no FLUSH request is re‐\nceived.\n\nfua = 0|1\nUse the FUA flag when writing data from persistent memory back to the  underlying  de‐\nvice.  Applicable only to persistent memory.\n\nnofua = 0|1\nDon't  use  the FUA flag when writing back data and send the FLUSH request afterwards.\nSome underlying devices perform better with fua, some with nofua.  Testing  is  neces‐\nsary to determine which.  Applicable only to persistent memory.\n\ncleaner = 0|1\nSetting  cleaner=1  enables  the  writecache  cleaner  mode in which data is gradually\nflushed from the cache.  If this is done prior to detaching the writecache,  then  the\nsplitcache  command  will  have little or no flushing to perform.  If not done before‐\nhand, the splitcache command enables the cleaner mode and waits for flushing  to  com‐\nplete  before  detaching  the  writecache.  Adding cleaner=0 to the splitcache command\nwill skip the cleaner mode, and any required flushing is performed in device suspend.\n\n"
                },
                {
                    "name": "dm-writecache using metadata profiles",
                    "content": "In addition to specifying writecache settings on the command line, they can also  be  set  in\nlvm.conf,  or in a profile file, using the allocation/cachesettings/writecache config struc‐\nture shown below.\n\nIt's possible to prepare a number of different profile files in the  /etc/lvm/profile  direc‐\ntory and specify the file name of the profile when starting writecache.\n\nExample\n# cat <<EOF > /etc/lvm/profile/cachewritecache.profile\nallocation {\ncachesettings {\nwritecache {\nhighwatermark=60\nwritebackjobs=1024\n}\n}\n}\nEOF\n\n# lvcreate -an -L10G --name fast vg /dev/fastssd\n# lvcreate --type writecache -L10G --name main  --cachevol fast \\\n--metadataprofile cachewritecache vg /dev/slowhdd\n"
                },
                {
                    "name": "dm-cache with separate data and metadata LVs",
                    "content": "Preferred  way  of  using  dm-cache is to place the cache metadata and cache data on separate\nLVs.  To do this, a \"cache pool\" is created, which is a special LV that  references  two  sub\nLVs, one for data and one for metadata.\n\nTo create a cache pool of given data size and let lvm2 calculate appropriate metadata size:\n\n# lvcreate --type cache-pool -L DataSize -n fast vg /dev/fastssd1\n\nTo  create  a  cache  pool from separate LV and let lvm2 calculate appropriate cache metadata\nsize:\n\n# lvcreate -n fast -L DataSize vg /dev/fastssd1\n# lvconvert --type cache-pool vg/fast /dev/fastssd1\n\nTo create a cache pool from two separate LVs:\n\n# lvcreate -n fast -L DataSize vg /dev/fastssd1\n# lvcreate -n fastmeta -L MetadataSize vg /dev/fastssd2\n# lvconvert --type cache-pool --poolmetadata fastmeta vg/fast\n\nThen use the cache pool LV to start caching the main LV:\n\n# lvconvert --type cache --cachepool fast vg/main\n\nA variation of the same procedure automatically creates a cache pool when caching is started.\nTo do this, use a standard LV as the --cachepool (this will hold cache data), and use another\nstandard LV as the --poolmetadata (this will hold cache metadata).  LVM will create  a  cache\npool LV from the two specified LVs, and use the cache pool to start caching the main LV.\n\n# lvcreate -n fast -L DataSize vg /dev/fastssd1\n# lvcreate -n fastmeta -L MetadataSize vg /dev/fastssd2\n# lvconvert --type cache --cachepool fast \\\n--poolmetadata fastmeta vg/main\n"
                },
                {
                    "name": "dm-cache cache modes",
                    "content": "The  default dm-cache cache mode is \"writethrough\".  Writethrough ensures that any data writ‐\nten will be stored both in the cache and on the origin LV.  The loss of a  device  associated\nwith the cache in this case would not mean the loss of any data.\n\nA second cache mode is \"writeback\".  Writeback delays writing data blocks from the cache back\nto  the  origin  LV.  This mode will increase performance, but the loss of a cache device can\nresult in lost data.\n\nWith the --cachemode option, the cache mode can be set when caching is started, or changed on\nan LV that is already cached.  The current cache mode can be displayed  with  the  cachemode\nreporting option:\n"
                },
                {
                    "name": "lvs -o+cache_mode VG/LV",
                    "content": "lvm.conf(5) allocation/cachemode\ndefines the default cache mode.\n\n# lvconvert --type cache --cachemode writethrough \\\n--cachepool fast vg/main\n\n# lvconvert --type cache --cachemode writethrough \\\n--cachevol fast  vg/main\n"
                },
                {
                    "name": "dm-cache chunk size",
                    "content": "The size of data blocks managed by dm-cache can be specified with the --chunksize option when\ncaching  is started.  The default unit is KiB.  The value must be a multiple of 32KiB between\n32KiB and 1GiB. Cache chunks bigger then 512KiB shall be only used when necessary.\n\nUsing a chunk size that is too large can result in wasteful use of the cache, in which  small\nreads and writes cause large sections of an LV to be stored in the cache. It can also require\nincreasing migration threshold which defaults to 2048 sectors (1 MiB). Lvm2 ensures migration\nthreshold  is at least 8 chunks in size. This may in some cases result in very high bandwidth\nload of transfering data between the cache LV and its cache origin LV.  However,  choosing  a\nchunk size that is too small can result in more overhead trying to manage the numerous chunks\nthat  become  mapped  into the cache.  Overhead can include both excessive CPU time searching\nfor chunks, and excessive memory tracking chunks.\n\nCommand to display the chunk size:\n"
                },
                {
                    "name": "lvs -o+chunksize VG/LV",
                    "content": "lvm.conf(5) allocation/cachepoolchunksize\n\ncontrols the default chunk size.\n\nThe default value is shown by:\n"
                },
                {
                    "name": "lvmconfig --type default allocation/cache_pool_chunk_size",
                    "content": "Checking migration threshold (in sectors) of running cached LV:"
                },
                {
                    "name": "lvs -o+kernel_cache_settings VG/LV",
                    "content": ""
                },
                {
                    "name": "dm-cache migration threshold",
                    "content": "Migrating data between the origin and cache LV uses bandwidth.  The user can set  a  throttle\nto  prevent more than a certain amount of migration occurring at any one time.  Currently dm-\ncache is not taking any account of normal io traffic going to the devices.\n\nUser can set migration threshold via cache  policy  settings  as  \"migrationthreshold=<#sec‐\ntors>\"  to  set  the maximum number of sectors being migrated, the default being 2048 sectors\n(1MiB).\n\nCommand to set migration threshold to 2MiB (4096 sectors):\n"
                },
                {
                    "name": "lvcreate --cachepolicy 'migration_threshold=4096' VG/LV",
                    "content": "Command to display the migration threshold:\n"
                },
                {
                    "name": "lvs -o+kernel_cache_settings,cache_settings VG/LV",
                    "content": ""
                },
                {
                    "name": "lvs -o+chunksize VG/LV",
                    "content": ""
                },
                {
                    "name": "dm-cache cache policy",
                    "content": "The dm-cache subsystem has additional per-LV parameters: the cache policy to use, and  possi‐\nbly  tunable  parameters for the cache policy.  Three policies are currently available: \"smq\"\nis the default policy, \"mq\" is an older implementation, and \"cleaner\" is used  to  force  the\ncache to write back (flush) all cached writes to the origin LV.\n\nThe older \"mq\" policy has a number of tunable parameters. The defaults are chosen to be suit‐\nable for the majority of systems, but in special circumstances, changing the settings can im‐\nprove performance.\n\nWith  the --cachepolicy and --cachesettings options, the cache policy and settings can be set\nwhen caching is started, or changed on an existing cached LV (both options can  be  used  to‐\ngether).   The  current  cache policy and settings can be displayed with the cachepolicy and\ncachesettings reporting options:\n"
                },
                {
                    "name": "lvs -o+cache_policy,cache_settings VG/LV",
                    "content": "Change the cache policy and settings of an existing LV.\n# lvchange --cachepolicy mq --cachesettings \\\n'migrationthreshold=2048 randomthreshold=4' vg/main\n\nlvm.conf(5) allocation/cachepolicy\ndefines the default cache policy.\n\nlvm.conf(5) allocation/cachesettings\ndefines the default cache settings.\n"
                },
                {
                    "name": "dm-cache using metadata profiles",
                    "content": "Cache pools allows to set a variety of options. Lots of these settings can  be  specified  in\nlvm.conf  or  profile  settings.  You  can  prepare  a  number  of  different profiles in the\n/etc/lvm/profile directory and just specify the metadata profile file name when caching LV or\ncreating cache-pool.  Check the output of lvmconfig --type default --withcomments for  a  de‐\ntailed description of all individual cache settings.\n\nExample\n# cat <<EOF > /etc/lvm/profile/cachebigchunk.profile\nallocation {\ncachepoolmetadatarequireseparatepvs=0\ncachepoolchunksize=512\ncachemetadataformat=2\ncachemode=\"writethrough\"\ncachepolicy=\"smq\"\ncachesettings {\nsmq {\nmigrationthreshold=8192\nrandomthreshold=4096\n}\n}\n}\nEOF\n\n# lvcreate --cache -L10G --metadataprofile cachebigchunk vg/main \\\n/dev/fastssd\n# lvcreate --cache -L10G vg/main --config \\\n'allocation/cachepoolchunksize=512' /dev/fastssd\n"
                },
                {
                    "name": "dm-cache spare metadata LV",
                    "content": "See  lvmthin(7)  for a description of the \"pool metadata spare\" LV.  The same concept is used\nfor cache pools.\n"
                },
                {
                    "name": "dm-cache metadata formats",
                    "content": "There are two disk formats for dm-cache metadata.  The metadata format can be specified  with\n--cachemetadataformat  when  caching  is started, and cannot be changed.  Format 2 has better\nperformance; it is more compact, and stores dirty bits in a separate  btree,  which  improves\nthe speed of shutting down the cache.  With auto, lvm selects the best option provided by the\ncurrent dm-cache kernel module.\n"
                },
                {
                    "name": "RAID1 cache device",
                    "content": "RAID1  can  be  used to create the fast LV holding the cache so that it can tolerate a device\nfailure.  (When using dm-cache with separate data and metadata LVs, each of the  sub-LVs  can\nuse RAID1.)\n\n# lvcreate -n main -L Size vg /dev/slow\n# lvcreate --type raid1 -m 1 -n fast -L Size vg /dev/ssd1 /dev/ssd2\n# lvconvert --type cache --cachevol fast vg/main\n"
                },
                {
                    "name": "dm-cache command shortcut",
                    "content": "A single command can be used to cache main LV with automatic creation of a cache-pool:\n\n# lvcreate --cache --size CacheDataSize VG/LV [FastPVs]\n\nor the longer variant\n\n# lvcreate --type cache --size CacheDataSize \\\n--name NameCachePool VG/LV [FastPVs]\n\nIn  this command, the specified LV already exists, and is the main LV to be cached.  The com‐\nmand creates a new cache pool with size and given name or the name is automatically  selected\nfrom  a  sequence  lvolXcpool, using the optionally specified fast PV(s) (typically an ssd).\nThen it attaches the new cache pool to the existing main LV to begin caching.\n\n(Note: ensure that the specified main LV is a standard LV.  If a cache pool LV is  mistakenly\nspecified, then the command does something different.)\n\n(Note:  the  type  option  is interpreted differently by this command than by normal lvcreate\ncommands in which --type specifies the type of the newly created LV.  In  this  case,  an  LV\nwith  type  cache-pool  is being created, and the existing main LV is being converted to type\ncache.)\n"
                }
            ]
        },
        "SEE ALSO": {
            "content": "lvm.conf(5), lvchange(8), lvcreate(8), lvdisplay(8), lvextend(8), lvremove(8), lvrename(8),\nlvresize(8), lvs(8),\nvgchange(8), vgmerge(8), vgreduce(8), vgsplit(8),\n\ncachecheck(8), cachedump(8), cacherepair(8)\n\nRed Hat, Inc                      LVM TOOLS 2.03.16(2) (2022-05-18)                      LVMCACHE(7)",
            "subsections": []
        }
    },
    "summary": "lvmcache — LVM caching",
    "flags": [],
    "examples": [],
    "see_also": [
        {
            "name": "lvm.conf",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/lvm.conf/5/json"
        },
        {
            "name": "lvchange",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvchange/8/json"
        },
        {
            "name": "lvcreate",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvcreate/8/json"
        },
        {
            "name": "lvdisplay",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvdisplay/8/json"
        },
        {
            "name": "lvextend",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvextend/8/json"
        },
        {
            "name": "lvremove",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvremove/8/json"
        },
        {
            "name": "lvrename",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvrename/8/json"
        },
        {
            "name": "lvresize",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvresize/8/json"
        },
        {
            "name": "lvs",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/lvs/8/json"
        },
        {
            "name": "vgchange",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/vgchange/8/json"
        },
        {
            "name": "vgmerge",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/vgmerge/8/json"
        },
        {
            "name": "vgreduce",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/vgreduce/8/json"
        },
        {
            "name": "vgsplit",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/vgsplit/8/json"
        },
        {
            "name": "cachecheck",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/cachecheck/8/json"
        },
        {
            "name": "cachedump",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/cachedump/8/json"
        },
        {
            "name": "cacherepair",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/cacherepair/8/json"
        }
    ]
}