{
    "mode": "man",
    "parameter": "e2fsck",
    "section": "8",
    "url": "https://www.chedong.com/phpMan.php/man/e2fsck/8/json",
    "generated": "2026-05-30T07:09:00Z",
    "synopsis": "e2fsck  [ -pacnyrdfkvtDFV ] [ -b superblock ] [ -B blocksize ] [ -l|-L badblocksfile ] [ -C\nfd ] [ -j external-journal ] [ -E extendedoptions ] [ -z undofile ] device",
    "sections": {
        "NAME": {
            "content": "e2fsck - check a Linux ext2/ext3/ext4 file system\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "e2fsck  [ -pacnyrdfkvtDFV ] [ -b superblock ] [ -B blocksize ] [ -l|-L badblocksfile ] [ -C\nfd ] [ -j external-journal ] [ -E extendedoptions ] [ -z undofile ] device\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "e2fsck is used to check the ext2/ext3/ext4 family of file systems.  For ext3  and  ext4  file\nsystems  that  use  a journal, if the system has been shut down uncleanly without any errors,\nnormally, after replaying the committed transactions  in the journal, the file system  should\nbe  marked  as clean.   Hence, for file systems that use journaling, e2fsck will normally re‐\nplay the journal and exit, unless its superblock indicates that further checking is required.\n\ndevice is a block device (e.g., /dev/sdc1) or file containing the file system.\n\nNote that in general it is not safe to run e2fsck on mounted file systems.  The  only  excep‐\ntion  is  if  the -n option is specified, and -c, -l, or -L options are not specified.   How‐\never, even if it is safe to do so, the results printed by e2fsck are not valid  if  the  file\nsystem  is  mounted.    If e2fsck asks whether or not you should check a file system which is\nmounted, the only correct answer is ``no''.  Only experts who really know what they are doing\nshould consider answering this question in any other way.\n\nIf  e2fsck is run in interactive mode (meaning that none of -y, -n, or -p are specified), the\nprogram will ask the user to fix each problem found in the file system.  A  response  of  'y'\nwill  fix  the  error; 'n' will leave the error unfixed; and 'a' will fix the problem and all\nsubsequent problems; pressing Enter will proceed with the default response, which is  printed\nbefore the question mark.  Pressing Control-C terminates e2fsck immediately.\n",
            "subsections": []
        },
        "OPTIONS": {
            "content": "",
            "subsections": [
                {
                    "name": "-a -p",
                    "content": "patibility only; it is suggested that people use -p option whenever possible.\n",
                    "flag": "-p"
                },
                {
                    "name": "-b",
                    "content": "Instead of using the normal superblock, use an alternative superblock specified by su‐\nperblock.   This  option  is  normally  used when the primary superblock has been cor‐\nrupted.  The location of backup superblocks is dependent on the file  system's  block‐\nsize, the number of blocks per group, and features such as sparsesuper.\n\nAdditional  backup superblocks can be determined by using the mke2fs program using the\n-n option to print out where the superblocks exist, supposing mke2fs is supplied  with\narguments  that  are  consistent with the file system's layout (e.g. blocksize, blocks\nper group, sparsesuper, etc.).\n\nIf an alternative superblock is specified and the file system is not opened read-only,\ne2fsck  will  make sure that the primary superblock is updated appropriately upon com‐\npletion of the file system check.\n",
                    "flag": "-b"
                },
                {
                    "name": "-B",
                    "content": "Normally, e2fsck will search for the superblock at various different block sizes in an\nattempt  to find the appropriate block size.  This search can be fooled in some cases.\nThis option forces e2fsck to only try locating the superblock at a  particular  block‐\nsize.  If the superblock is not found, e2fsck will terminate with a fatal error.\n",
                    "flag": "-B"
                },
                {
                    "name": "-c",
                    "content": "device in order to find any bad blocks.  If any bad blocks are found, they  are  added\nto  the  bad  block inode to prevent them from being allocated to a file or directory.\nIf this option is specified twice, then the bad block scan will be done using  a  non-\ndestructive read-write test.\n",
                    "flag": "-c"
                },
                {
                    "name": "-C",
                    "content": "scriptor so that the progress of the file system check can be monitored.  This  option\nis typically used by programs which are running e2fsck.  If the file descriptor number\nis negative, then absolute value of the file descriptor will be used, and the progress\ninformation  will  be  suppressed  initially.   It can later be enabled by sending the\ne2fsck process a SIGUSR1 signal.  If the file descriptor specified is 0,  e2fsck  will\nprint  a  completion  bar as it goes about its business.  This requires that e2fsck is\nrunning on a video console or terminal.\n",
                    "flag": "-C"
                },
                {
                    "name": "-d",
                    "content": "",
                    "flag": "-d"
                },
                {
                    "name": "-D",
                    "content": "directories,  either  by re-indexing them if the file system supports directory index‐\ning,  or by sorting and compressing directories for smaller directories, or  for  file\nsystems using traditional linear directories.\n\nEven  without  the  -D option, e2fsck may sometimes optimize a few directories --- for\nexample, if directory indexing is enabled and a directory is  not  indexed  and  would\nbenefit  from  being  indexed, or if the index structures are corrupted and need to be\nrebuilt.  The -D option forces all directories in the file  system  to  be  optimized.\nThis  can  sometimes  make them a little smaller and slightly faster to search, but in\npractice, you should rarely need to use this option.\n\nThe -D option will detect directory entries with duplicate names in  a  single  direc‐\ntory, which e2fsck normally does not enforce for performance reasons.\n",
                    "flag": "-D"
                },
                {
                    "name": "-E",
                    "content": "Set  e2fsck  extended  options.  Extended options are comma separated, and may take an\nargument using the equals ('=') sign.  The following options are supported:\n\neaver=extendedattributeversion\nSet the version of the extended attribute blocks which e2fsck will require\nwhile  checking  the  file system.  The version number may be 1 or 2.  The\ndefault extended attribute version format is 2.\n\njournalonly\nOnly replay the journal if required, but do not perform any further checks\nor repairs.\n\nfragcheck\nDuring  pass  1,  print  a detailed report of any discontiguous blocks for\nfiles in the file system.\n\ndiscard\nAttempt to discard free blocks and unused inode blocks after the full file\nsystem  check  (discarding  blocks  is  useful  on solid state devices and\nsparse / thin-provisioned storage). Note that discard is done  in  pass  5\nAFTER  the file system has been fully checked and only if it does not con‐\ntain recognizable errors. However there might be cases where  e2fsck  does\nnot  fully recognize a problem and hence in this case this option may pre‐\nvent you from further manual data recovery.\n\nnodiscard\nDo not attempt to discard free blocks and unused inode blocks. This option\nis exactly the opposite of discard option. This is set as default.\n\nnooptimizeextents\nDo  not offer to optimize the extent tree by eliminating unnecessary width\nor  depth.   This  can  also  be  enabled  in  the  options   section   of\n/etc/e2fsck.conf.\n\noptimizeextents\nOffer  to  optimize  the  extent  tree by eliminating unnecessary width or\ndepth.    This   is   the   default   unless   otherwise   specified    in\n/etc/e2fsck.conf.\n\ninodecountfullmap\nTrade  off using memory for speed when checking a file system with a large\nnumber of hard-linked files.  The amount of  memory  required  is  propor‐\ntional  to  the  number of inodes in the file system.  For large file sys‐\ntems, this can be gigabytes of memory.  (For example, a 40TB  file  system\nwith  2.8  billion inodes will consume an additional 5.7 GB memory if this\noptimization is enabled.)  This optimization can also be  enabled  in  the\noptions section of /etc/e2fsck.conf.\n\nnoinodecountfullmap\nDisable  the inodecountfullmap optimization.  This is the default unless\notherwise specified in /etc/e2fsck.conf.\n\nreadaheadkb\nUse this many KiB of memory to pre-fetch metadata in the hopes of reducing\ne2fsck  runtime.  By default, this is set to the size of two block groups'\ninode tables (typically 4MiB on a  regular  ext4  file  system);  if  this\namount  is  more  than  1/50th of total physical memory, readahead is dis‐\nabled.  Set this to zero to disable readahead entirely.\n\nbmap2extent\nConvert block-mapped files to extent-mapped files.\n\nfixesonly\nOnly fix damaged metadata; do not optimize htree directories  or  compress\nextent  trees.  This option is incompatible with the -D and -E bmap2extent\noptions.\n\ncheckencoding\nForce verification of encoded filenames in  case-insensitive  directories.\nThis is the default mode if the file system has the strict flag enabled.\n\nunshareblocks\nIf  the  file  system  has shared blocks, with the shared blocks read-only\nfeature enabled, then this will unshare all shared blocks  and  unset  the\nread-only  feature  bit. If there is not enough free space then the opera‐\ntion will fail.  If the file system does not have  the  read-only  feature\nbit,  but  has shared blocks anyway, then this option will have no effect.\nNote when using this option, if there is no free space  to  clone  blocks,\nthere is no prompt to delete files and instead the operation will fail.\n\nNote that unshareblocks implies the \"-f\" option to ensure that all passes\nare run. Additionally, if \"-n\" is also  specified,  e2fsck  will  simulate\ntrying  to  allocate  enough space to deduplicate. If this fails, the exit\ncode will be non-zero.\n",
                    "flag": "-E"
                },
                {
                    "name": "-f",
                    "content": "",
                    "flag": "-f"
                },
                {
                    "name": "-F",
                    "content": "doing e2fsck time trials.\n",
                    "flag": "-F"
                },
                {
                    "name": "-j",
                    "content": "Set the pathname where the external-journal for this file system can be found.\n",
                    "flag": "-j"
                },
                {
                    "name": "-k -c",
                    "content": "preserved, and any new bad blocks found by running badblocks(8) will be added  to  the\nexisting bad blocks list.\n",
                    "flag": "-c"
                },
                {
                    "name": "-l",
                    "content": "Add  the  block  numbers  listed  in the file specified by filename to the list of bad\nblocks.  The format of this file is the same as the one generated by the  badblocks(8)\nprogram.   Note  that the block numbers are based on the blocksize of the file system.\nHence, badblocks(8) must be given the blocksize of the file system in order to  obtain\ncorrect  results.   As  a result, it is much simpler and safer to use the -c option to\ne2fsck, since it will assure that the correct parameters are passed to  the  badblocks\nprogram.\n",
                    "flag": "-l"
                },
                {
                    "name": "-L",
                    "content": "Set  the bad blocks list to be the list of blocks specified by filename.  (This option\nis the same as the -l option, except the bad blocks list is cleared before the  blocks\nlisted in the file are added to the bad blocks list.)\n",
                    "flag": "-L"
                },
                {
                    "name": "-n",
                    "content": "e2fsck to be used non-interactively.  This option may not be  specified  at  the  same\ntime as the -p or -y options.\n",
                    "flag": "-n"
                },
                {
                    "name": "-p",
                    "content": "tomatically fix any file system problems that can be safely fixed without human inter‐\nvention.   If e2fsck discovers a problem which may require the system administrator to\ntake additional corrective action, e2fsck will print a description of the problem  and\nthen  exit  with  the  value 4 logically or'ed into the exit code.  (See the EXIT CODE\nsection.)  This option is normally used by the system's boot scripts.  It may  not  be\nspecified at the same time as the -n or -y options.\n",
                    "flag": "-p"
                },
                {
                    "name": "-r",
                    "content": "",
                    "flag": "-r"
                },
                {
                    "name": "-t",
                    "content": "statistics are printed on a pass by pass basis.\n",
                    "flag": "-t"
                },
                {
                    "name": "-v",
                    "content": "",
                    "flag": "-v"
                },
                {
                    "name": "-V",
                    "content": "",
                    "flag": "-V"
                },
                {
                    "name": "-y",
                    "content": "tively.  This option may not be specified at the same time as the -n or -p options.\n",
                    "flag": "-y"
                },
                {
                    "name": "-z",
                    "content": "Before overwriting a file system block, write the old contents of the block to an undo\nfile.  This undo file can be used with e2undo(8) to restore the old  contents  of  the\nfile system should something go wrong.  If the empty string is passed as the undofile\nargument, the undo file will be written to a file named  e2fsck-device.e2undo  in  the\ndirectory specified via the E2FSPROGSUNDODIR environment variable.\n\nWARNING: The undo file cannot be used to recover from a power or system crash.\n",
                    "flag": "-z"
                }
            ]
        },
        "EXIT CODE": {
            "content": "The exit code returned by e2fsck is the sum of the following conditions:\n0    - No errors\n1    - File system errors corrected\n2    - File system errors corrected, system should\nbe rebooted\n4    - File system errors left uncorrected\n8    - Operational error\n16   - Usage or syntax error\n32   - E2fsck canceled by user request\n128  - Shared library error\n",
            "subsections": []
        },
        "SIGNALS": {
            "content": "The following signals have the following effect when sent to e2fsck.\n\nSIGUSR1\nThis  signal  causes  e2fsck to start displaying a completion bar or emitting progress\ninformation.  (See discussion of the -C option.)\n\nSIGUSR2\nThis signal causes e2fsck to stop displaying a completion bar or emitting progress in‐\nformation.\n",
            "subsections": []
        },
        "REPORTING BUGS": {
            "content": "Almost  any  piece  of  software  will  have bugs.  If you manage to find a file system which\ncauses e2fsck to crash, or which e2fsck is unable to repair, please report it to the author.\n\nPlease include as much information as possible in your bug report.  Ideally, include  a  com‐\nplete  transcript  of the e2fsck run, so I can see exactly what error messages are displayed.\n(Make sure the messages printed by e2fsck are in English; if your system has been  configured\nso  that  e2fsck's  messages  have  been translated into another language, please set the the\nLCALL environment variable to C so that the transcript of e2fsck's output will be useful  to\nme.)   If  you  have a writable file system where the transcript can be stored, the script(1)\nprogram is a handy way to save the output of e2fsck to a file.\n\nIt is also useful to send the output of dumpe2fs(8).  If a specific inode or inodes seems  to\nbe  giving  e2fsck  trouble,  try  running  the debugfs(8) command and send the output of the\nstat(1u) command run on the relevant inode(s).  If the inode is a directory, the debugfs dump\ncommand  will  allow you to extract the contents of the directory inode, which can sent to me\nafter being first run through uuencode(1).  The most useful data you can send to help  repro‐\nduce  the  bug is a compressed raw image dump of the file system, generated using e2image(8).\nSee the e2image(8) man page for more details.\n\nAlways include the full version string which e2fsck displays when it is run, so I know  which\nversion you are running.\n",
            "subsections": []
        },
        "ENVIRONMENT": {
            "content": "E2FSCKCONFIG\nDetermines the location of the configuration file (see e2fsck.conf(5)).\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "This version of e2fsck was written by Theodore Ts'o <tytso@mit.edu>.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "e2fsck.conf(5), badblocks(8), dumpe2fs(8), debugfs(8), e2image(8), mke2fs(8), tune2fs(8)\n\n\n\nE2fsprogs version 1.46.5                    December 2021                                  E2FSCK(8)",
            "subsections": []
        }
    },
    "summary": "e2fsck - check a Linux ext2/ext3/ext4 file system",
    "flags": [
        {
            "flag": "-p",
            "long": null,
            "arg": null,
            "description": "patibility only; it is suggested that people use -p option whenever possible."
        },
        {
            "flag": "-b",
            "long": null,
            "arg": null,
            "description": "Instead of using the normal superblock, use an alternative superblock specified by su‐ perblock. This option is normally used when the primary superblock has been cor‐ rupted. The location of backup superblocks is dependent on the file system's block‐ size, the number of blocks per group, and features such as sparsesuper. Additional backup superblocks can be determined by using the mke2fs program using the -n option to print out where the superblocks exist, supposing mke2fs is supplied with arguments that are consistent with the file system's layout (e.g. blocksize, blocks per group, sparsesuper, etc.). If an alternative superblock is specified and the file system is not opened read-only, e2fsck will make sure that the primary superblock is updated appropriately upon com‐ pletion of the file system check."
        },
        {
            "flag": "-B",
            "long": null,
            "arg": null,
            "description": "Normally, e2fsck will search for the superblock at various different block sizes in an attempt to find the appropriate block size. This search can be fooled in some cases. This option forces e2fsck to only try locating the superblock at a particular block‐ size. If the superblock is not found, e2fsck will terminate with a fatal error."
        },
        {
            "flag": "-c",
            "long": null,
            "arg": null,
            "description": "device in order to find any bad blocks. If any bad blocks are found, they are added to the bad block inode to prevent them from being allocated to a file or directory. If this option is specified twice, then the bad block scan will be done using a non- destructive read-write test."
        },
        {
            "flag": "-C",
            "long": null,
            "arg": null,
            "description": "scriptor so that the progress of the file system check can be monitored. This option is typically used by programs which are running e2fsck. If the file descriptor number is negative, then absolute value of the file descriptor will be used, and the progress information will be suppressed initially. It can later be enabled by sending the e2fsck process a SIGUSR1 signal. If the file descriptor specified is 0, e2fsck will print a completion bar as it goes about its business. This requires that e2fsck is running on a video console or terminal."
        },
        {
            "flag": "-d",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-D",
            "long": null,
            "arg": null,
            "description": "directories, either by re-indexing them if the file system supports directory index‐ ing, or by sorting and compressing directories for smaller directories, or for file systems using traditional linear directories. Even without the -D option, e2fsck may sometimes optimize a few directories --- for example, if directory indexing is enabled and a directory is not indexed and would benefit from being indexed, or if the index structures are corrupted and need to be rebuilt. The -D option forces all directories in the file system to be optimized. This can sometimes make them a little smaller and slightly faster to search, but in practice, you should rarely need to use this option. The -D option will detect directory entries with duplicate names in a single direc‐ tory, which e2fsck normally does not enforce for performance reasons."
        },
        {
            "flag": "-E",
            "long": null,
            "arg": null,
            "description": "Set e2fsck extended options. Extended options are comma separated, and may take an argument using the equals ('=') sign. The following options are supported: eaver=extendedattributeversion Set the version of the extended attribute blocks which e2fsck will require while checking the file system. The version number may be 1 or 2. The default extended attribute version format is 2. journalonly Only replay the journal if required, but do not perform any further checks or repairs. fragcheck During pass 1, print a detailed report of any discontiguous blocks for files in the file system. discard Attempt to discard free blocks and unused inode blocks after the full file system check (discarding blocks is useful on solid state devices and sparse / thin-provisioned storage). Note that discard is done in pass 5 AFTER the file system has been fully checked and only if it does not con‐ tain recognizable errors. However there might be cases where e2fsck does not fully recognize a problem and hence in this case this option may pre‐ vent you from further manual data recovery. nodiscard Do not attempt to discard free blocks and unused inode blocks. This option is exactly the opposite of discard option. This is set as default. nooptimizeextents Do not offer to optimize the extent tree by eliminating unnecessary width or depth. This can also be enabled in the options section of /etc/e2fsck.conf. optimizeextents Offer to optimize the extent tree by eliminating unnecessary width or depth. This is the default unless otherwise specified in /etc/e2fsck.conf. inodecountfullmap Trade off using memory for speed when checking a file system with a large number of hard-linked files. The amount of memory required is propor‐ tional to the number of inodes in the file system. For large file sys‐ tems, this can be gigabytes of memory. (For example, a 40TB file system with 2.8 billion inodes will consume an additional 5.7 GB memory if this optimization is enabled.) This optimization can also be enabled in the options section of /etc/e2fsck.conf. noinodecountfullmap Disable the inodecountfullmap optimization. This is the default unless otherwise specified in /etc/e2fsck.conf. readaheadkb Use this many KiB of memory to pre-fetch metadata in the hopes of reducing e2fsck runtime. By default, this is set to the size of two block groups' inode tables (typically 4MiB on a regular ext4 file system); if this amount is more than 1/50th of total physical memory, readahead is dis‐ abled. Set this to zero to disable readahead entirely. bmap2extent Convert block-mapped files to extent-mapped files. fixesonly Only fix damaged metadata; do not optimize htree directories or compress extent trees. This option is incompatible with the -D and -E bmap2extent options. checkencoding Force verification of encoded filenames in case-insensitive directories. This is the default mode if the file system has the strict flag enabled. unshareblocks If the file system has shared blocks, with the shared blocks read-only feature enabled, then this will unshare all shared blocks and unset the read-only feature bit. If there is not enough free space then the opera‐ tion will fail. If the file system does not have the read-only feature bit, but has shared blocks anyway, then this option will have no effect. Note when using this option, if there is no free space to clone blocks, there is no prompt to delete files and instead the operation will fail. Note that unshareblocks implies the \"-f\" option to ensure that all passes are run. Additionally, if \"-n\" is also specified, e2fsck will simulate trying to allocate enough space to deduplicate. If this fails, the exit code will be non-zero."
        },
        {
            "flag": "-f",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-F",
            "long": null,
            "arg": null,
            "description": "doing e2fsck time trials."
        },
        {
            "flag": "-j",
            "long": null,
            "arg": null,
            "description": "Set the pathname where the external-journal for this file system can be found."
        },
        {
            "flag": "-c",
            "long": null,
            "arg": null,
            "description": "preserved, and any new bad blocks found by running badblocks(8) will be added to the existing bad blocks list."
        },
        {
            "flag": "-l",
            "long": null,
            "arg": null,
            "description": "Add the block numbers listed in the file specified by filename to the list of bad blocks. The format of this file is the same as the one generated by the badblocks(8) program. Note that the block numbers are based on the blocksize of the file system. Hence, badblocks(8) must be given the blocksize of the file system in order to obtain correct results. As a result, it is much simpler and safer to use the -c option to e2fsck, since it will assure that the correct parameters are passed to the badblocks program."
        },
        {
            "flag": "-L",
            "long": null,
            "arg": null,
            "description": "Set the bad blocks list to be the list of blocks specified by filename. (This option is the same as the -l option, except the bad blocks list is cleared before the blocks listed in the file are added to the bad blocks list.)"
        },
        {
            "flag": "-n",
            "long": null,
            "arg": null,
            "description": "e2fsck to be used non-interactively. This option may not be specified at the same time as the -p or -y options."
        },
        {
            "flag": "-p",
            "long": null,
            "arg": null,
            "description": "tomatically fix any file system problems that can be safely fixed without human inter‐ vention. If e2fsck discovers a problem which may require the system administrator to take additional corrective action, e2fsck will print a description of the problem and then exit with the value 4 logically or'ed into the exit code. (See the EXIT CODE section.) This option is normally used by the system's boot scripts. It may not be specified at the same time as the -n or -y options."
        },
        {
            "flag": "-r",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-t",
            "long": null,
            "arg": null,
            "description": "statistics are printed on a pass by pass basis."
        },
        {
            "flag": "-v",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-V",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-y",
            "long": null,
            "arg": null,
            "description": "tively. This option may not be specified at the same time as the -n or -p options."
        },
        {
            "flag": "-z",
            "long": null,
            "arg": null,
            "description": "Before overwriting a file system block, write the old contents of the block to an undo file. This undo file can be used with e2undo(8) to restore the old contents of the file system should something go wrong. If the empty string is passed as the undofile argument, the undo file will be written to a file named e2fsck-device.e2undo in the directory specified via the E2FSPROGSUNDODIR environment variable. WARNING: The undo file cannot be used to recover from a power or system crash."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "e2fsck.conf",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/e2fsck.conf/5/json"
        },
        {
            "name": "badblocks",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/badblocks/8/json"
        },
        {
            "name": "dumpe2fs",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/dumpe2fs/8/json"
        },
        {
            "name": "debugfs",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/debugfs/8/json"
        },
        {
            "name": "e2image",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/e2image/8/json"
        },
        {
            "name": "mke2fs",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/mke2fs/8/json"
        },
        {
            "name": "tune2fs",
            "section": "8",
            "url": "https://www.chedong.com/phpMan.php/man/tune2fs/8/json"
        }
    ]
}