From 7ffccaf0c3b4d4979d7d74bab3d79d9541a6e665 Mon Sep 17 00:00:00 2001
From: David Sterba <dsterba@suse.cz>
Date: Tue, 14 Apr 2015 17:37:23 +0200
Subject: btrfs-progs: Documentaion: rename to .asciidoc

A few minor benefits:

* editors set highliting according to the extensions
* web access to the git repository (github) renders the .asciidoc
  files:
  * we can link to them from the wiki
  * the files are editable via browser and such editations can be
    submitted for merge easily

Signed-off-by: David Sterba <dsterba@suse.cz>
---
 Documentation/Makefile.in                     |  66 ++++----
 Documentation/btrfs-balance.asciidoc          | 140 +++++++++++++++++
 Documentation/btrfs-balance.txt               | 140 -----------------
 Documentation/btrfs-check.asciidoc            |  58 +++++++
 Documentation/btrfs-check.txt                 |  58 -------
 Documentation/btrfs-convert.asciidoc          |  59 +++++++
 Documentation/btrfs-convert.txt               |  59 -------
 Documentation/btrfs-debug-tree.asciidoc       |  38 +++++
 Documentation/btrfs-debug-tree.txt            |  38 -----
 Documentation/btrfs-device.asciidoc           | 142 +++++++++++++++++
 Documentation/btrfs-device.txt                | 142 -----------------
 Documentation/btrfs-filesystem.asciidoc       | 169 ++++++++++++++++++++
 Documentation/btrfs-filesystem.txt            | 169 --------------------
 Documentation/btrfs-find-root.asciidoc        |  35 +++++
 Documentation/btrfs-find-root.txt             |  35 -----
 Documentation/btrfs-image.asciidoc            |  66 ++++++++
 Documentation/btrfs-image.txt                 |  66 --------
 Documentation/btrfs-inspect-internal.asciidoc |  67 ++++++++
 Documentation/btrfs-inspect-internal.txt      |  67 --------
 Documentation/btrfs-map-logical.asciidoc      |  37 +++++
 Documentation/btrfs-map-logical.txt           |  37 -----
 Documentation/btrfs-mount.asciidoc            | 213 ++++++++++++++++++++++++++
 Documentation/btrfs-mount.txt                 | 213 --------------------------
 Documentation/btrfs-property.asciidoc         |  73 +++++++++
 Documentation/btrfs-property.txt              |  73 ---------
 Documentation/btrfs-qgroup.asciidoc           | 133 ++++++++++++++++
 Documentation/btrfs-qgroup.txt                | 133 ----------------
 Documentation/btrfs-quota.asciidoc            |  56 +++++++
 Documentation/btrfs-quota.txt                 |  56 -------
 Documentation/btrfs-receive.asciidoc          |  59 +++++++
 Documentation/btrfs-receive.txt               |  59 -------
 Documentation/btrfs-replace.asciidoc          |  81 ++++++++++
 Documentation/btrfs-replace.txt               |  81 ----------
 Documentation/btrfs-rescue.asciidoc           |  58 +++++++
 Documentation/btrfs-rescue.txt                |  58 -------
 Documentation/btrfs-restore.asciidoc          |  85 ++++++++++
 Documentation/btrfs-restore.txt               |  85 ----------
 Documentation/btrfs-scrub.asciidoc            |  94 ++++++++++++
 Documentation/btrfs-scrub.txt                 |  94 ------------
 Documentation/btrfs-send.asciidoc             |  58 +++++++
 Documentation/btrfs-send.txt                  |  58 -------
 Documentation/btrfs-show-super.asciidoc       |  50 ++++++
 Documentation/btrfs-show-super.txt            |  50 ------
 Documentation/btrfs-subvolume.asciidoc        | 183 ++++++++++++++++++++++
 Documentation/btrfs-subvolume.txt             | 183 ----------------------
 Documentation/btrfs-zero-log.asciidoc         |  45 ++++++
 Documentation/btrfs-zero-log.txt              |  45 ------
 Documentation/btrfs.asciidoc                  | 121 +++++++++++++++
 Documentation/btrfs.txt                       | 121 ---------------
 Documentation/btrfstune.asciidoc              |  44 ++++++
 Documentation/btrfstune.txt                   |  44 ------
 Documentation/fsck.btrfs.asciidoc             |  51 ++++++
 Documentation/fsck.btrfs.txt                  |  51 ------
 Documentation/mkfs.btrfs.asciidoc             | 140 +++++++++++++++++
 Documentation/mkfs.btrfs.txt                  | 140 -----------------
 55 files changed, 2388 insertions(+), 2388 deletions(-)
 create mode 100644 Documentation/btrfs-balance.asciidoc
 delete mode 100644 Documentation/btrfs-balance.txt
 create mode 100644 Documentation/btrfs-check.asciidoc
 delete mode 100644 Documentation/btrfs-check.txt
 create mode 100644 Documentation/btrfs-convert.asciidoc
 delete mode 100644 Documentation/btrfs-convert.txt
 create mode 100644 Documentation/btrfs-debug-tree.asciidoc
 delete mode 100644 Documentation/btrfs-debug-tree.txt
 create mode 100644 Documentation/btrfs-device.asciidoc
 delete mode 100644 Documentation/btrfs-device.txt
 create mode 100644 Documentation/btrfs-filesystem.asciidoc
 delete mode 100644 Documentation/btrfs-filesystem.txt
 create mode 100644 Documentation/btrfs-find-root.asciidoc
 delete mode 100644 Documentation/btrfs-find-root.txt
 create mode 100644 Documentation/btrfs-image.asciidoc
 delete mode 100644 Documentation/btrfs-image.txt
 create mode 100644 Documentation/btrfs-inspect-internal.asciidoc
 delete mode 100644 Documentation/btrfs-inspect-internal.txt
 create mode 100644 Documentation/btrfs-map-logical.asciidoc
 delete mode 100644 Documentation/btrfs-map-logical.txt
 create mode 100644 Documentation/btrfs-mount.asciidoc
 delete mode 100644 Documentation/btrfs-mount.txt
 create mode 100644 Documentation/btrfs-property.asciidoc
 delete mode 100644 Documentation/btrfs-property.txt
 create mode 100644 Documentation/btrfs-qgroup.asciidoc
 delete mode 100644 Documentation/btrfs-qgroup.txt
 create mode 100644 Documentation/btrfs-quota.asciidoc
 delete mode 100644 Documentation/btrfs-quota.txt
 create mode 100644 Documentation/btrfs-receive.asciidoc
 delete mode 100644 Documentation/btrfs-receive.txt
 create mode 100644 Documentation/btrfs-replace.asciidoc
 delete mode 100644 Documentation/btrfs-replace.txt
 create mode 100644 Documentation/btrfs-rescue.asciidoc
 delete mode 100644 Documentation/btrfs-rescue.txt
 create mode 100644 Documentation/btrfs-restore.asciidoc
 delete mode 100644 Documentation/btrfs-restore.txt
 create mode 100644 Documentation/btrfs-scrub.asciidoc
 delete mode 100644 Documentation/btrfs-scrub.txt
 create mode 100644 Documentation/btrfs-send.asciidoc
 delete mode 100644 Documentation/btrfs-send.txt
 create mode 100644 Documentation/btrfs-show-super.asciidoc
 delete mode 100644 Documentation/btrfs-show-super.txt
 create mode 100644 Documentation/btrfs-subvolume.asciidoc
 delete mode 100644 Documentation/btrfs-subvolume.txt
 create mode 100644 Documentation/btrfs-zero-log.asciidoc
 delete mode 100644 Documentation/btrfs-zero-log.txt
 create mode 100644 Documentation/btrfs.asciidoc
 delete mode 100644 Documentation/btrfs.txt
 create mode 100644 Documentation/btrfstune.asciidoc
 delete mode 100644 Documentation/btrfstune.txt
 create mode 100644 Documentation/fsck.btrfs.asciidoc
 delete mode 100644 Documentation/fsck.btrfs.txt
 create mode 100644 Documentation/mkfs.btrfs.asciidoc
 delete mode 100644 Documentation/mkfs.btrfs.txt

diff --git a/Documentation/Makefile.in b/Documentation/Makefile.in
index cb09e2a8..695311dc 100644
--- a/Documentation/Makefile.in
+++ b/Documentation/Makefile.in
@@ -2,46 +2,46 @@
 MAN8_TXT =
 
 # Top level commands
-MAN8_TXT += btrfs.txt
-MAN8_TXT += btrfs-convert.txt
-MAN8_TXT += btrfs-debug-tree.txt
-MAN8_TXT += btrfs-find-root.txt
-MAN8_TXT += btrfs-image.txt
-MAN8_TXT += btrfs-map-logical.txt
-MAN8_TXT += btrfs-show-super.txt
-MAN8_TXT += btrfstune.txt
-MAN8_TXT += btrfs-zero-log.txt
-MAN8_TXT += fsck.btrfs.txt
-MAN8_TXT += mkfs.btrfs.txt
+MAN8_TXT += btrfs.asciidoc
+MAN8_TXT += btrfs-convert.asciidoc
+MAN8_TXT += btrfs-debug-tree.asciidoc
+MAN8_TXT += btrfs-find-root.asciidoc
+MAN8_TXT += btrfs-image.asciidoc
+MAN8_TXT += btrfs-map-logical.asciidoc
+MAN8_TXT += btrfs-show-super.asciidoc
+MAN8_TXT += btrfstune.asciidoc
+MAN8_TXT += btrfs-zero-log.asciidoc
+MAN8_TXT += fsck.btrfs.asciidoc
+MAN8_TXT += mkfs.btrfs.asciidoc
 
 # Sub commands for btrfs
-MAN8_TXT += btrfs-subvolume.txt
-MAN8_TXT += btrfs-filesystem.txt
-MAN8_TXT += btrfs-balance.txt
-MAN8_TXT += btrfs-device.txt
-MAN8_TXT += btrfs-scrub.txt
-MAN8_TXT += btrfs-check.txt
-MAN8_TXT += btrfs-rescue.txt
-MAN8_TXT += btrfs-inspect-internal.txt
-MAN8_TXT += btrfs-send.txt
-MAN8_TXT += btrfs-receive.txt
-MAN8_TXT += btrfs-quota.txt
-MAN8_TXT += btrfs-qgroup.txt
-MAN8_TXT += btrfs-replace.txt
-MAN8_TXT += btrfs-restore.txt
-MAN8_TXT += btrfs-property.txt
+MAN8_TXT += btrfs-subvolume.asciidoc
+MAN8_TXT += btrfs-filesystem.asciidoc
+MAN8_TXT += btrfs-balance.asciidoc
+MAN8_TXT += btrfs-device.asciidoc
+MAN8_TXT += btrfs-scrub.asciidoc
+MAN8_TXT += btrfs-check.asciidoc
+MAN8_TXT += btrfs-rescue.asciidoc
+MAN8_TXT += btrfs-inspect-internal.asciidoc
+MAN8_TXT += btrfs-send.asciidoc
+MAN8_TXT += btrfs-receive.asciidoc
+MAN8_TXT += btrfs-quota.asciidoc
+MAN8_TXT += btrfs-qgroup.asciidoc
+MAN8_TXT += btrfs-replace.asciidoc
+MAN8_TXT += btrfs-restore.asciidoc
+MAN8_TXT += btrfs-property.asciidoc
 
 # Mount manpage
-MAN5_TXT += btrfs-mount.txt
+MAN5_TXT += btrfs-mount.asciidoc
 
 MAN_TXT = $(MAN8_TXT) $(MAN5_TXT)
-MAN_XML = $(patsubst %.txt,%.xml,$(MAN_TXT))
+MAN_XML = $(patsubst %.asciidoc,%.xml,$(MAN_TXT))
 
-DOC_MAN5 = $(patsubst %.txt,%.5,$(MAN5_TXT))
-GZ_MAN5 = $(patsubst %.txt,%.5.gz,$(MAN5_TXT))
+DOC_MAN5 = $(patsubst %.asciidoc,%.5,$(MAN5_TXT))
+GZ_MAN5 = $(patsubst %.asciidoc,%.5.gz,$(MAN5_TXT))
 
-DOC_MAN8 = $(patsubst %.txt,%.8,$(MAN8_TXT))
-GZ_MAN8 = $(patsubst %.txt,%.8.gz,$(MAN8_TXT))
+DOC_MAN8 = $(patsubst %.asciidoc,%.8,$(MAN8_TXT))
+GZ_MAN8 = $(patsubst %.asciidoc,%.8.gz,$(MAN8_TXT))
 
 mandir ?= $(prefix)/share/man
 man8dir = $(mandir)/man8
@@ -115,7 +115,7 @@ clean:
 	$(QUIET_XMLTO)$(RM) -f $@ && \
 	$(XMLTO) -m $(MANPAGE_XSL) $(XMLTO_EXTRA) man $<
 
-%.xml : %.txt asciidoc.conf
+%.xml : %.asciidoc asciidoc.conf
 	$(QUIET_ASCIIDOC)$(RM) -f $@+ $@ && \
 	$(ASCIIDOC) -b docbook -d manpage -f asciidoc.conf \
 		$(ASCIIDOC_EXTRA) -abtrfs_version=$(BTRFS_VERSION) \
diff --git a/Documentation/btrfs-balance.asciidoc b/Documentation/btrfs-balance.asciidoc
new file mode 100644
index 00000000..6d2fd0c3
--- /dev/null
+++ b/Documentation/btrfs-balance.asciidoc
@@ -0,0 +1,140 @@
+btrfs-balance(8)
+================
+
+NAME
+----
+btrfs-balance - balance btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs balance* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs balance* is used to balance chunks in a btrfs filesystem across
+multiple or even single device.
+
+See `btrfs-device`(8) for more details about the effect on device management.
+
+NOTE: The balance subcommand also exists under the *filesystem* namespace. This
+still works for backward compatibility but is deprecated and should not be
+used anymore.
+
+NOTE: A short syntax *btrfs balance <path>* works due to backward compatibility
+but is deprecated and should not be used anymore. Use *btrfs balance start*
+command instead.
+
+SUBCOMMAND
+----------
+*cancel* <path>::
+Cancel running or paused balance.
+
+*pause* <path>::
+Pause running balance.
+
+*resume* <path>::
+Resume interrupted balance.
+
+*start* [options] <path>::
+Balance chunks across the devices *online*.
++
+Balance and/or convert (change allocation profile of) chunks that
+passed all filters in a comma-separated list of filters for a
+particular chunk type.
+If filter list is not given balance all chunks of that type.
+In case none of the -d, -m or -s options is
+given balance all chunks in a filesystem.
++
+`Options`
++
+-d[<filters>]::::
+act on data chunks. See `FILTERS` section for details about <filters>.
+-m[<filters>]::::
+act on metadata chunks. See `FILTERS` section for details about <filters>.
+-s[<filters>]::::
+act on system chunks (only under -f). See `FILTERS` section for details about <filters>.
+-v::::
+be verbose
+-f::::
+force reducing of metadata integrity
+
+*status* [-v] <path>::
+Show status of running or paused balance.
++
+If '-v' option is given, output will be verbose.
+
+FILTERS
+-------
+From kernel 3.3 onwards, btrfs balance can limit its action to a subset of the
+full filesystem, and can be used to change the replication configuration (e.g.
+moving data from single to RAID-1). This functionality is accessed through the
+'-d', '-m' or '-s' options to btrfs balance start, which filter on data,
+metadata and system blocks respectively.
+
+A filter has the following stucture: ::
+'type'[='params'][,'type'=...]
+
+The available types are:
+
+*profiles*::
+Balances only block groups with the given replication profiles. Parameters
+are a list of profile names separated by |.
+
+*usage*::
+Balances only block groups with usage under the given percentage. The
+value of 0 is allowed and will clean up completely unused block groups, this
+should not require any new space allocated. You may want to use usage=0 in
+case balance is returnin ENOSPC and your filesystem is not too full.
+
+*devid*::
+Balances only block groups which have at least one chunk on the given
+device (by btrfs device ID -- use btrfs fi show to list device IDs)
+
+*drange*::
+Balances only block groups which overlap with the given byte range on any
+device. (Use in conjunction with "devid" to filter on a specific device). The
+parameter is a range specified as <start..end>.
+
+*vrange*::
+Balances only block groups which overlap with the given byte range in the
+filesystem's internal virtual address space. This is the address space that
+most reports from btrfs in the kernel log use. The parameter is a range
+specified as <start..end>.
+
+*convert*::
+Convert each selected block group to the given profile name identified by
+parameters.
+
+*limit*::
+Process only given number of chunks, after all filters apply. This can be used
+to specifically target a chunk in connection with other filters (drange,
+vrange) or just simply limit the amount of work done by a single balance run.
+
+*soft*::
+Takes no parameters. Only has meaning when converting between profiles.
+When doing convert from one profile to another and soft mode is on,
+restriper won't touch chunks that already have the target profile. This is
+useful if e.g. half of the FS was converted earlier.
++
+The soft mode switch is (like every other filter) per-type. This means
+that we can convert for example meta chunks the "hard" way while converting
+data chunks selectively with soft switch.
+
+Profile names, used in profiles and convert are one of: 'raid0', 'raid1',
+'raid10', 'raid5', 'raid6', 'dup', 'single'.
+
+EXIT STATUS
+-----------
+*btrfs balance* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-device`(8)
diff --git a/Documentation/btrfs-balance.txt b/Documentation/btrfs-balance.txt
deleted file mode 100644
index 6d2fd0c3..00000000
--- a/Documentation/btrfs-balance.txt
+++ /dev/null
@@ -1,140 +0,0 @@
-btrfs-balance(8)
-================
-
-NAME
-----
-btrfs-balance - balance btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs balance* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs balance* is used to balance chunks in a btrfs filesystem across
-multiple or even single device.
-
-See `btrfs-device`(8) for more details about the effect on device management.
-
-NOTE: The balance subcommand also exists under the *filesystem* namespace. This
-still works for backward compatibility but is deprecated and should not be
-used anymore.
-
-NOTE: A short syntax *btrfs balance <path>* works due to backward compatibility
-but is deprecated and should not be used anymore. Use *btrfs balance start*
-command instead.
-
-SUBCOMMAND
-----------
-*cancel* <path>::
-Cancel running or paused balance.
-
-*pause* <path>::
-Pause running balance.
-
-*resume* <path>::
-Resume interrupted balance.
-
-*start* [options] <path>::
-Balance chunks across the devices *online*.
-+
-Balance and/or convert (change allocation profile of) chunks that
-passed all filters in a comma-separated list of filters for a
-particular chunk type.
-If filter list is not given balance all chunks of that type.
-In case none of the -d, -m or -s options is
-given balance all chunks in a filesystem.
-+
-`Options`
-+
--d[<filters>]::::
-act on data chunks. See `FILTERS` section for details about <filters>.
--m[<filters>]::::
-act on metadata chunks. See `FILTERS` section for details about <filters>.
--s[<filters>]::::
-act on system chunks (only under -f). See `FILTERS` section for details about <filters>.
--v::::
-be verbose
--f::::
-force reducing of metadata integrity
-
-*status* [-v] <path>::
-Show status of running or paused balance.
-+
-If '-v' option is given, output will be verbose.
-
-FILTERS
--------
-From kernel 3.3 onwards, btrfs balance can limit its action to a subset of the
-full filesystem, and can be used to change the replication configuration (e.g.
-moving data from single to RAID-1). This functionality is accessed through the
-'-d', '-m' or '-s' options to btrfs balance start, which filter on data,
-metadata and system blocks respectively.
-
-A filter has the following stucture: ::
-'type'[='params'][,'type'=...]
-
-The available types are:
-
-*profiles*::
-Balances only block groups with the given replication profiles. Parameters
-are a list of profile names separated by |.
-
-*usage*::
-Balances only block groups with usage under the given percentage. The
-value of 0 is allowed and will clean up completely unused block groups, this
-should not require any new space allocated. You may want to use usage=0 in
-case balance is returnin ENOSPC and your filesystem is not too full.
-
-*devid*::
-Balances only block groups which have at least one chunk on the given
-device (by btrfs device ID -- use btrfs fi show to list device IDs)
-
-*drange*::
-Balances only block groups which overlap with the given byte range on any
-device. (Use in conjunction with "devid" to filter on a specific device). The
-parameter is a range specified as <start..end>.
-
-*vrange*::
-Balances only block groups which overlap with the given byte range in the
-filesystem's internal virtual address space. This is the address space that
-most reports from btrfs in the kernel log use. The parameter is a range
-specified as <start..end>.
-
-*convert*::
-Convert each selected block group to the given profile name identified by
-parameters.
-
-*limit*::
-Process only given number of chunks, after all filters apply. This can be used
-to specifically target a chunk in connection with other filters (drange,
-vrange) or just simply limit the amount of work done by a single balance run.
-
-*soft*::
-Takes no parameters. Only has meaning when converting between profiles.
-When doing convert from one profile to another and soft mode is on,
-restriper won't touch chunks that already have the target profile. This is
-useful if e.g. half of the FS was converted earlier.
-+
-The soft mode switch is (like every other filter) per-type. This means
-that we can convert for example meta chunks the "hard" way while converting
-data chunks selectively with soft switch.
-
-Profile names, used in profiles and convert are one of: 'raid0', 'raid1',
-'raid10', 'raid5', 'raid6', 'dup', 'single'.
-
-EXIT STATUS
------------
-*btrfs balance* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-device`(8)
diff --git a/Documentation/btrfs-check.asciidoc b/Documentation/btrfs-check.asciidoc
new file mode 100644
index 00000000..f8d8ab4d
--- /dev/null
+++ b/Documentation/btrfs-check.asciidoc
@@ -0,0 +1,58 @@
+btrfs-check(8)
+==============
+
+NAME
+----
+btrfs-check - check or repair an unmounted btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs check* [options] <device>
+
+DESCRIPTION
+-----------
+*btrfs check* is used to check or repair an unmounted btrfs filesystem.
+
+NOTE: Since btrfs is under development, the *btrfs check* capabilities are
+continuously enhanced. It's highly recommended to read the following btrfs
+wiki before executing *btrfs check* with '--repair' option: +
+https://btrfs.wiki.kernel.org/index.php/Btrfsck
+
+*btrfsck* is an alias of *btrfs check* command and is now deprecated.
+
+OPTIONS
+-------
+-s|--super <superblock>::
+use <superblock>th superblock copy, valid values are 0 up to 2 if the
+respective superblock offset is within the fileystem
+--repair::
+try to repair the filesystem
+--init-csum-tree::
+create a new CRC tree and recalculate all checksums
+--init-extent-tree::
+create a new extent tree
+--check-data-csum::
+verify checkums of data blocks
+--qgroup-report::
+verify qgroup accounting and compare against filesystem accounting
+--subvol-extents <subvolid>::
+show extent state for a subvolume
+--tree-root <bytenr>::
+use the given bytenr for the tree root
+
+EXIT STATUS
+-----------
+*btrfs check* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-scrub`(8),
+`btrfs-rescue`(8)
diff --git a/Documentation/btrfs-check.txt b/Documentation/btrfs-check.txt
deleted file mode 100644
index f8d8ab4d..00000000
--- a/Documentation/btrfs-check.txt
+++ /dev/null
@@ -1,58 +0,0 @@
-btrfs-check(8)
-==============
-
-NAME
-----
-btrfs-check - check or repair an unmounted btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs check* [options] <device>
-
-DESCRIPTION
------------
-*btrfs check* is used to check or repair an unmounted btrfs filesystem.
-
-NOTE: Since btrfs is under development, the *btrfs check* capabilities are
-continuously enhanced. It's highly recommended to read the following btrfs
-wiki before executing *btrfs check* with '--repair' option: +
-https://btrfs.wiki.kernel.org/index.php/Btrfsck
-
-*btrfsck* is an alias of *btrfs check* command and is now deprecated.
-
-OPTIONS
--------
--s|--super <superblock>::
-use <superblock>th superblock copy, valid values are 0 up to 2 if the
-respective superblock offset is within the fileystem
---repair::
-try to repair the filesystem
---init-csum-tree::
-create a new CRC tree and recalculate all checksums
---init-extent-tree::
-create a new extent tree
---check-data-csum::
-verify checkums of data blocks
---qgroup-report::
-verify qgroup accounting and compare against filesystem accounting
---subvol-extents <subvolid>::
-show extent state for a subvolume
---tree-root <bytenr>::
-use the given bytenr for the tree root
-
-EXIT STATUS
------------
-*btrfs check* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-scrub`(8),
-`btrfs-rescue`(8)
diff --git a/Documentation/btrfs-convert.asciidoc b/Documentation/btrfs-convert.asciidoc
new file mode 100644
index 00000000..09510fa6
--- /dev/null
+++ b/Documentation/btrfs-convert.asciidoc
@@ -0,0 +1,59 @@
+btrfs-convert(8)
+================
+
+NAME
+----
+btrfs-convert - convert from ext2/3/4 filesystem to btrfs or rollback
+
+SYNOPSIS
+--------
+*btrfs-convert* [options] <device>
+
+DESCRIPTION
+-----------
+*btrfs-convert* is used to convert existed ext2/3/4 to btrfs filesystem,
+and the original filesystem image is accessible as from separate subvolume
+named 'ext2_saved' as file image.
+
+WARNING: If one hopes to rollback to ext2/3/4, they should not execute
+*btrfs balance* command on converted btrfs, since it will change the extent
+layout and make *btrfs-convert* unable to rollback.
+
+NOTE: If one is satisfied with converted btrfs, and not longer wants to
+rollback to ext2/3/4, it is highly recommended to remove 'ext2_saved' subvolume
+and execute *btrfs filesystem defragment* and *btrfs balance* command on the
+converted btrfs.
+
+OPTIONS
+-------
+-d|--no-datasum::
+Disable data checksum calculations and set NODATASUM file flag. This can speed
+up the conversion.
+-i|--no-xattr::
+Ignore xattrs and ACLs.
+-n|--no-inline::
+Disable inlining of small files to metadata blocks.
+-N|--nodesize <SIZE>::
+Set filesystem nodesize, the tree block size in which btrfs stores data.
+The default value is 16KB (16384) or the page size, whichever is bigger.
+Must be a multiple of the sectorsize, but not larger than 65536.
+-r|--rollback::
+Roll back to ext2fs.
+-l|--label <LABEL>::
+set filesystem label during conversion.
+-L|--copy-label::
+use label from the converted filesystem.
+-p|--progress::
+Show progress of conversion, on by default.
+--no-progress::
+Disable detailed progress and show only the main phases of conversion.
+
+EXIT STATUS
+-----------
+*btrfs-convert* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
+
diff --git a/Documentation/btrfs-convert.txt b/Documentation/btrfs-convert.txt
deleted file mode 100644
index 09510fa6..00000000
--- a/Documentation/btrfs-convert.txt
+++ /dev/null
@@ -1,59 +0,0 @@
-btrfs-convert(8)
-================
-
-NAME
-----
-btrfs-convert - convert from ext2/3/4 filesystem to btrfs or rollback
-
-SYNOPSIS
---------
-*btrfs-convert* [options] <device>
-
-DESCRIPTION
------------
-*btrfs-convert* is used to convert existed ext2/3/4 to btrfs filesystem,
-and the original filesystem image is accessible as from separate subvolume
-named 'ext2_saved' as file image.
-
-WARNING: If one hopes to rollback to ext2/3/4, they should not execute
-*btrfs balance* command on converted btrfs, since it will change the extent
-layout and make *btrfs-convert* unable to rollback.
-
-NOTE: If one is satisfied with converted btrfs, and not longer wants to
-rollback to ext2/3/4, it is highly recommended to remove 'ext2_saved' subvolume
-and execute *btrfs filesystem defragment* and *btrfs balance* command on the
-converted btrfs.
-
-OPTIONS
--------
--d|--no-datasum::
-Disable data checksum calculations and set NODATASUM file flag. This can speed
-up the conversion.
--i|--no-xattr::
-Ignore xattrs and ACLs.
--n|--no-inline::
-Disable inlining of small files to metadata blocks.
--N|--nodesize <SIZE>::
-Set filesystem nodesize, the tree block size in which btrfs stores data.
-The default value is 16KB (16384) or the page size, whichever is bigger.
-Must be a multiple of the sectorsize, but not larger than 65536.
--r|--rollback::
-Roll back to ext2fs.
--l|--label <LABEL>::
-set filesystem label during conversion.
--L|--copy-label::
-use label from the converted filesystem.
--p|--progress::
-Show progress of conversion, on by default.
---no-progress::
-Disable detailed progress and show only the main phases of conversion.
-
-EXIT STATUS
------------
-*btrfs-convert* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
-
diff --git a/Documentation/btrfs-debug-tree.asciidoc b/Documentation/btrfs-debug-tree.asciidoc
new file mode 100644
index 00000000..23fc1156
--- /dev/null
+++ b/Documentation/btrfs-debug-tree.asciidoc
@@ -0,0 +1,38 @@
+btrfs-debug-tree(8)
+===================
+
+NAME
+----
+btrfs-debug-tree - dump btrfs filesystem metadata into stdout
+
+SYNOPSIS
+--------
+*btrfs-debug-tree* [options] <device>
+
+DESCRIPTION
+-----------
+*btrfs-debug-tree* is used to dump the whole tree of the given device.
+
+This is maybe useful for analyzing filesystem state or inconsistence and has
+a positive educational effect on understanding the internal structure.
+<device> is the device file where the filesystem is stored.
+
+OPTIONS
+-------
+-e::
+Print detailed extents info.
+-d::
+Print info of btrfs device and root tree dirs only.
+-r::
+Print info of roots only.
+-b <block_num>::
+Print info of the specified block only.
+
+EXIT STATUS
+-----------
+*btrfs-debug-tree* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-debug-tree.txt b/Documentation/btrfs-debug-tree.txt
deleted file mode 100644
index 23fc1156..00000000
--- a/Documentation/btrfs-debug-tree.txt
+++ /dev/null
@@ -1,38 +0,0 @@
-btrfs-debug-tree(8)
-===================
-
-NAME
-----
-btrfs-debug-tree - dump btrfs filesystem metadata into stdout
-
-SYNOPSIS
---------
-*btrfs-debug-tree* [options] <device>
-
-DESCRIPTION
------------
-*btrfs-debug-tree* is used to dump the whole tree of the given device.
-
-This is maybe useful for analyzing filesystem state or inconsistence and has
-a positive educational effect on understanding the internal structure.
-<device> is the device file where the filesystem is stored.
-
-OPTIONS
--------
--e::
-Print detailed extents info.
--d::
-Print info of btrfs device and root tree dirs only.
--r::
-Print info of roots only.
--b <block_num>::
-Print info of the specified block only.
-
-EXIT STATUS
------------
-*btrfs-debug-tree* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-device.asciidoc b/Documentation/btrfs-device.asciidoc
new file mode 100644
index 00000000..075ccc5a
--- /dev/null
+++ b/Documentation/btrfs-device.asciidoc
@@ -0,0 +1,142 @@
+btrfs-device(8)
+===============
+
+NAME
+----
+btrfs-device - control btrfs devices
+
+SYNOPSIS
+--------
+*btrfs device* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs device* is used to control the btrfs devices, since btrfs can be used
+across several devices, *btrfs device* is used for multiple device management.
+
+DEVICE MANAGEMENT
+-----------------
+Btrfs filesystem is capable to manage multiple devices.
+
+Btrfs filesystem uses different profiles to manage different RAID level, and
+use balance to rebuild chunks, also devices can be added/removed/replace
+online.
+
+Profile::
+Btrfs filesystem uses data/metadata profiles to manage allocation/duplication
+mechanism. +
+Profiles like RAID level can be assigned to data and metadata separately.
++
+See `mkfs.btrfs`(8) for more details.
+
+RAID level::
+Btrfs filesystem supports most of the standard RAID level: 0/1/5/6/10. +
+RAID levels can be assigned at mkfs time or online.
++
+See `mkfs.btrfs`(8) for mkfs time RAID level assign and `btrfs-balance`(8) for
+online RAID level assign.
++
+NOTE: Since btrfs is under heavy development especially the RAID5/6 support,
+it is *highly* recommended to read the follow btrfs wiki page to get more
+updated details on RAID5/6: +
+https://btrfs.wiki.kernel.org/index.php/RAID56
+
+Balance::
+`btrfs-balance`(8) subcommand can be used to balance or rebuild chunks to the
+desired profile.
++
+Due to the fact that balance can rebuild/recovery chunks according to its RAID
+duplication if possible, so when using RAID1/5/6/10 with some devices failed
+and you just added a new device to btrfs using `btrfs-device`(8), you should
+run `btrfs-balance`(8) to rebuild the chunks.
++
+See `btrfs-balance`(8) for more details.
+
+Device add/remove/replace::
+Device can be added/removed using `btrfs-replace`(8) subcommand and replaced
+using `btrfs-replace`(8).
++
+When device is removed or replaced, btrfs will do the chunk rebuild if needed.
++
+See `btrfs-replace`(8) and this man page for more details.
+
+SUBCOMMAND
+----------
+*add* [-Kf] <dev> [<dev>...] <path>::
+Add device(s) to the filesystem identified by <path>.
++
+If applicable, a whole device discard (TRIM) operation is performed.
++
+`Options`
++
+-K|--nodiscard::::
+do not perform discard by default
+-f|--force::::
+force overwrite of existing filesystem on the given disk(s)
+
+*delete* <dev> [<dev>...] <path>::
+Remove device(s) from a filesystem identified by <path>.
+
+*ready* <device>::
+Check device to see if it has all of it's devices in cache for mounting.
+
+*scan* [(--all-devices|-d)|<device> [<device>...]]::
+Scan devices for a btrfs filesystem.
++
+If one or more devices are passed, these are scanned for a btrfs filesystem.
+If no devices are passed, btrfs uses block devices containing btrfs
+filesystem as listed by blkid.
+Finally, if '--all-devices' or '-d' is passed, all the devices under /dev are
+scanned.
+
+*stats* [-z] <path>|<device>::
+Read and print the device IO stats for all mounted devices of the filesystem
+identified by <path> or for a single <device>.
++
+`Options`
++
+-z::::
+Reset stats to zero after reading them.
+
+*usage* [options] <path> [<path>...]::
+Show detailed information about internal allocations in devices.
++
+`Options`
++
+-b|--raw::::
+raw numbers in bytes, without the 'B' suffix
+-h|--human-readable::::
+print human friendly numbers, base 1024, this is the default
+-H::::
+print human friendly numbers, base 1000
+--iec::::
+select the 1024 base for the following options, according to the IEC standard
+--si::::
+select the 1000 base for the following options, according to the SI standard
+-k|--kbytes::::
+show sizes in KiB, or kB with --si
+-m|--mbytes::::
+show sizes in MiB, or MB with --si
+-g|--gbytes::::
+show sizes in GiB, or GB with --si
+-t|--tbytes::::
+show sizes in TiB, or TB with --si
+
+If conflicting options are passed, the last one takes precedence.
+
+EXIT STATUS
+-----------
+*btrfs device* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-replace`(8),
+`btrfs-balance`(8)
diff --git a/Documentation/btrfs-device.txt b/Documentation/btrfs-device.txt
deleted file mode 100644
index 075ccc5a..00000000
--- a/Documentation/btrfs-device.txt
+++ /dev/null
@@ -1,142 +0,0 @@
-btrfs-device(8)
-===============
-
-NAME
-----
-btrfs-device - control btrfs devices
-
-SYNOPSIS
---------
-*btrfs device* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs device* is used to control the btrfs devices, since btrfs can be used
-across several devices, *btrfs device* is used for multiple device management.
-
-DEVICE MANAGEMENT
------------------
-Btrfs filesystem is capable to manage multiple devices.
-
-Btrfs filesystem uses different profiles to manage different RAID level, and
-use balance to rebuild chunks, also devices can be added/removed/replace
-online.
-
-Profile::
-Btrfs filesystem uses data/metadata profiles to manage allocation/duplication
-mechanism. +
-Profiles like RAID level can be assigned to data and metadata separately.
-+
-See `mkfs.btrfs`(8) for more details.
-
-RAID level::
-Btrfs filesystem supports most of the standard RAID level: 0/1/5/6/10. +
-RAID levels can be assigned at mkfs time or online.
-+
-See `mkfs.btrfs`(8) for mkfs time RAID level assign and `btrfs-balance`(8) for
-online RAID level assign.
-+
-NOTE: Since btrfs is under heavy development especially the RAID5/6 support,
-it is *highly* recommended to read the follow btrfs wiki page to get more
-updated details on RAID5/6: +
-https://btrfs.wiki.kernel.org/index.php/RAID56
-
-Balance::
-`btrfs-balance`(8) subcommand can be used to balance or rebuild chunks to the
-desired profile.
-+
-Due to the fact that balance can rebuild/recovery chunks according to its RAID
-duplication if possible, so when using RAID1/5/6/10 with some devices failed
-and you just added a new device to btrfs using `btrfs-device`(8), you should
-run `btrfs-balance`(8) to rebuild the chunks.
-+
-See `btrfs-balance`(8) for more details.
-
-Device add/remove/replace::
-Device can be added/removed using `btrfs-replace`(8) subcommand and replaced
-using `btrfs-replace`(8).
-+
-When device is removed or replaced, btrfs will do the chunk rebuild if needed.
-+
-See `btrfs-replace`(8) and this man page for more details.
-
-SUBCOMMAND
-----------
-*add* [-Kf] <dev> [<dev>...] <path>::
-Add device(s) to the filesystem identified by <path>.
-+
-If applicable, a whole device discard (TRIM) operation is performed.
-+
-`Options`
-+
--K|--nodiscard::::
-do not perform discard by default
--f|--force::::
-force overwrite of existing filesystem on the given disk(s)
-
-*delete* <dev> [<dev>...] <path>::
-Remove device(s) from a filesystem identified by <path>.
-
-*ready* <device>::
-Check device to see if it has all of it's devices in cache for mounting.
-
-*scan* [(--all-devices|-d)|<device> [<device>...]]::
-Scan devices for a btrfs filesystem.
-+
-If one or more devices are passed, these are scanned for a btrfs filesystem.
-If no devices are passed, btrfs uses block devices containing btrfs
-filesystem as listed by blkid.
-Finally, if '--all-devices' or '-d' is passed, all the devices under /dev are
-scanned.
-
-*stats* [-z] <path>|<device>::
-Read and print the device IO stats for all mounted devices of the filesystem
-identified by <path> or for a single <device>.
-+
-`Options`
-+
--z::::
-Reset stats to zero after reading them.
-
-*usage* [options] <path> [<path>...]::
-Show detailed information about internal allocations in devices.
-+
-`Options`
-+
--b|--raw::::
-raw numbers in bytes, without the 'B' suffix
--h|--human-readable::::
-print human friendly numbers, base 1024, this is the default
--H::::
-print human friendly numbers, base 1000
---iec::::
-select the 1024 base for the following options, according to the IEC standard
---si::::
-select the 1000 base for the following options, according to the SI standard
--k|--kbytes::::
-show sizes in KiB, or kB with --si
--m|--mbytes::::
-show sizes in MiB, or MB with --si
--g|--gbytes::::
-show sizes in GiB, or GB with --si
--t|--tbytes::::
-show sizes in TiB, or TB with --si
-
-If conflicting options are passed, the last one takes precedence.
-
-EXIT STATUS
------------
-*btrfs device* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-replace`(8),
-`btrfs-balance`(8)
diff --git a/Documentation/btrfs-filesystem.asciidoc b/Documentation/btrfs-filesystem.asciidoc
new file mode 100644
index 00000000..cefdc8ea
--- /dev/null
+++ b/Documentation/btrfs-filesystem.asciidoc
@@ -0,0 +1,169 @@
+btrfs-filesystem(8)
+===================
+
+NAME
+----
+btrfs-filesystem - control btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs filesystem* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs filesystem* is used to do the filesystem level control jobs, including
+all the regular filesystem operations like setting/getting label,
+resizing, defragment.
+
+SUBCOMMAND
+----------
+*df* [options] <path>::
+Show space usage information for a mount point.
++
+`Options`
++
+-b|--raw::::
+raw numbers in bytes, without the 'B' suffix
+-h|--human-readable::::
+print human friendly numbers, base 1024, this is the default
+-H::::
+print human friendly numbers, base 1000
+--iec::::
+select the 1024 base for the following options, according to the IEC standard
+--si::::
+select the 1000 base for the following options, according to the SI standard
+-k|--kbytes::::
+show sizes in KiB, or kB with --si
+-m|--mbytes::::
+show sizes in MiB, or MB with --si
+-g|--gbytes::::
+show sizes in GiB, or GB with --si
+-t|--tbytes::::
+show sizes in TiB, or TB with --si
++
+If conflicting options are passed, the last one takes precedence.
+
+*defragment* [options] <file>|<dir> [<file>|<dir>...]::
+Defragment file data and/or directory metadata *online*.
++
+If '-r' is passed, files in dir will be defragmented recursively.
+The start position and the number of bytes to defragment can be specified by
+start and len using '-s' and '-l' options below.
+Any extent bigger than threshold given by '-t' option, will be considered
+already defragged.
+Use 0 to take the kernel default.
+You can also turn on compression in defragment operations.
++
+`Options`
++
+-v::::
+be verbose
+-c::::
+compress file contents while defragmenting
+-r::::
+defragment files recursively
+-f::::
+flush filesystem after defragmenting
+-s <start>[kKmMgGtTpPeE]::::
+defragment only from byte <start> onward
+-l <len>[kKmMgGtTpPeE]::::
+defragment only up to <len> bytes
+-t <size>[kKmMgGtTpPeE]::::
+defragment only files at least <size> bytes big
++
+For <start>, <len>, <size> it is possible to append
+units designator: \'K', \'M', \'G', \'T', \'P', or \'E', which represent
+KiB, MiB, GiB, TiB, PiB, or EiB, respectively. Case does not matter.
++
+WARNING: defragmenting with kernels up to 2.6.37 will unlink COW-ed copies of data,
+don't use it if you use snapshots, have de-duplicated your data or made
+copies with `cp --reflink`.
+
+*label* [<dev>|<mountpoint>] [<newlabel>]::
+Show or update the label of a filesystem.
++
+[<device>|<mountpoint>] is used to identify the filesystem.
+If a newlabel optional argument is passed, the label is changed.
++
+NOTE: the maximum allowable length shall be less than 256 chars
+
+// Some wording are extracted by the resize2fs man page
+*resize* [<devid>:][+/-]<size>[kKmMgGtTpPeE]|[<devid>:]max <path>::
+Resize a filesystem identified by <path> for the underlying device
+devid *online*. +
+The devid can be found with *btrfs filesystem show* and
+defaults to 1 if not specified.
+The <size> parameter specifies the new size of the filesystem.
+If the prefix + or - is present the size is increased or decreased
+by the quantity <size>.
+If no units are specified, the unit of the <size> parameter defaults to
+bytes. Optionally, the size parameter may be suffixed by one of the following
+units designators: \'K', \'M', \'G', \'T', \'P', or \'E', which represent
+KiB, MiB, GiB, TiB, PiB, or EiB, respectively. Case does not matter.
++
+If \'max' is passed, the filesystem will occupy all available space on the
+device devid.
++
+The resize command does not manipulate the size of underlying
+partition.  If you wish to enlarge/reduce a filesystem, you must make sure you
+can expand the partition before enlarging the filesystem and shrink the
+partition after reducing the size of the filesystem.  This can done using
+`fdisk`(8) or `parted`(8) to delete the existing partition and recreate
+it with the new desired size.  When recreating the partition make sure to use
+the same starting disk cylinder as before.
+
+*show* [--mounted|--all-devices|<path>|<uuid>|<device>|<label>]::
+Show the btrfs filesystem with some additional info.
++
+If no option nor <path>|<uuid>|<device>|<label> is passed, btrfs shows
+information of all the btrfs filesystem both mounted and unmounted.
+If '--mounted' is passed, it would probe btrfs kernel to list mounted btrfs
+filesystem(s);
+If '--all-devices' is passed, all the devices under /dev are scanned;
+otherwise the devices list is extracted from the /proc/partitions file.
+
+*sync* <path>::
+Force a sync for the filesystem identified by <path>.
+
+*usage* [options] <path> [<path>...]::
+Show detailed information about internal filesystem usage.
++
+`Options`
++
+-b|--raw::::
+raw numbers in bytes, without the 'B' suffix
+-h|--human-readable::::
+print human friendly numbers, base 1024, this is the default
+-H::::
+print human friendly numbers, base 1000
+--iec::::
+select the 1024 base for the following options, according to the IEC standard
+--si::::
+select the 1000 base for the following options, according to the SI standard
+-k|--kbytes::::
+show sizes in KiB, or kB with --si
+-m|--mbytes::::
+show sizes in MiB, or MB with --si
+-g|--gbytes::::
+show sizes in GiB, or GB with --si
+-t|--tbytes::::
+show sizes in TiB, or TB with --si
+-T::::
+show data in tabular format
++
+If conflicting options are passed, the last one takes precedence.
+
+EXIT STATUS
+-----------
+*btrfs filesystem* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
deleted file mode 100644
index cefdc8ea..00000000
--- a/Documentation/btrfs-filesystem.txt
+++ /dev/null
@@ -1,169 +0,0 @@
-btrfs-filesystem(8)
-===================
-
-NAME
-----
-btrfs-filesystem - control btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs filesystem* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs filesystem* is used to do the filesystem level control jobs, including
-all the regular filesystem operations like setting/getting label,
-resizing, defragment.
-
-SUBCOMMAND
-----------
-*df* [options] <path>::
-Show space usage information for a mount point.
-+
-`Options`
-+
--b|--raw::::
-raw numbers in bytes, without the 'B' suffix
--h|--human-readable::::
-print human friendly numbers, base 1024, this is the default
--H::::
-print human friendly numbers, base 1000
---iec::::
-select the 1024 base for the following options, according to the IEC standard
---si::::
-select the 1000 base for the following options, according to the SI standard
--k|--kbytes::::
-show sizes in KiB, or kB with --si
--m|--mbytes::::
-show sizes in MiB, or MB with --si
--g|--gbytes::::
-show sizes in GiB, or GB with --si
--t|--tbytes::::
-show sizes in TiB, or TB with --si
-+
-If conflicting options are passed, the last one takes precedence.
-
-*defragment* [options] <file>|<dir> [<file>|<dir>...]::
-Defragment file data and/or directory metadata *online*.
-+
-If '-r' is passed, files in dir will be defragmented recursively.
-The start position and the number of bytes to defragment can be specified by
-start and len using '-s' and '-l' options below.
-Any extent bigger than threshold given by '-t' option, will be considered
-already defragged.
-Use 0 to take the kernel default.
-You can also turn on compression in defragment operations.
-+
-`Options`
-+
--v::::
-be verbose
--c::::
-compress file contents while defragmenting
--r::::
-defragment files recursively
--f::::
-flush filesystem after defragmenting
--s <start>[kKmMgGtTpPeE]::::
-defragment only from byte <start> onward
--l <len>[kKmMgGtTpPeE]::::
-defragment only up to <len> bytes
--t <size>[kKmMgGtTpPeE]::::
-defragment only files at least <size> bytes big
-+
-For <start>, <len>, <size> it is possible to append
-units designator: \'K', \'M', \'G', \'T', \'P', or \'E', which represent
-KiB, MiB, GiB, TiB, PiB, or EiB, respectively. Case does not matter.
-+
-WARNING: defragmenting with kernels up to 2.6.37 will unlink COW-ed copies of data,
-don't use it if you use snapshots, have de-duplicated your data or made
-copies with `cp --reflink`.
-
-*label* [<dev>|<mountpoint>] [<newlabel>]::
-Show or update the label of a filesystem.
-+
-[<device>|<mountpoint>] is used to identify the filesystem.
-If a newlabel optional argument is passed, the label is changed.
-+
-NOTE: the maximum allowable length shall be less than 256 chars
-
-// Some wording are extracted by the resize2fs man page
-*resize* [<devid>:][+/-]<size>[kKmMgGtTpPeE]|[<devid>:]max <path>::
-Resize a filesystem identified by <path> for the underlying device
-devid *online*. +
-The devid can be found with *btrfs filesystem show* and
-defaults to 1 if not specified.
-The <size> parameter specifies the new size of the filesystem.
-If the prefix + or - is present the size is increased or decreased
-by the quantity <size>.
-If no units are specified, the unit of the <size> parameter defaults to
-bytes. Optionally, the size parameter may be suffixed by one of the following
-units designators: \'K', \'M', \'G', \'T', \'P', or \'E', which represent
-KiB, MiB, GiB, TiB, PiB, or EiB, respectively. Case does not matter.
-+
-If \'max' is passed, the filesystem will occupy all available space on the
-device devid.
-+
-The resize command does not manipulate the size of underlying
-partition.  If you wish to enlarge/reduce a filesystem, you must make sure you
-can expand the partition before enlarging the filesystem and shrink the
-partition after reducing the size of the filesystem.  This can done using
-`fdisk`(8) or `parted`(8) to delete the existing partition and recreate
-it with the new desired size.  When recreating the partition make sure to use
-the same starting disk cylinder as before.
-
-*show* [--mounted|--all-devices|<path>|<uuid>|<device>|<label>]::
-Show the btrfs filesystem with some additional info.
-+
-If no option nor <path>|<uuid>|<device>|<label> is passed, btrfs shows
-information of all the btrfs filesystem both mounted and unmounted.
-If '--mounted' is passed, it would probe btrfs kernel to list mounted btrfs
-filesystem(s);
-If '--all-devices' is passed, all the devices under /dev are scanned;
-otherwise the devices list is extracted from the /proc/partitions file.
-
-*sync* <path>::
-Force a sync for the filesystem identified by <path>.
-
-*usage* [options] <path> [<path>...]::
-Show detailed information about internal filesystem usage.
-+
-`Options`
-+
--b|--raw::::
-raw numbers in bytes, without the 'B' suffix
--h|--human-readable::::
-print human friendly numbers, base 1024, this is the default
--H::::
-print human friendly numbers, base 1000
---iec::::
-select the 1024 base for the following options, according to the IEC standard
---si::::
-select the 1000 base for the following options, according to the SI standard
--k|--kbytes::::
-show sizes in KiB, or kB with --si
--m|--mbytes::::
-show sizes in MiB, or MB with --si
--g|--gbytes::::
-show sizes in GiB, or GB with --si
--t|--tbytes::::
-show sizes in TiB, or TB with --si
--T::::
-show data in tabular format
-+
-If conflicting options are passed, the last one takes precedence.
-
-EXIT STATUS
------------
-*btrfs filesystem* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
diff --git a/Documentation/btrfs-find-root.asciidoc b/Documentation/btrfs-find-root.asciidoc
new file mode 100644
index 00000000..e04cd3e8
--- /dev/null
+++ b/Documentation/btrfs-find-root.asciidoc
@@ -0,0 +1,35 @@
+btrfs-find-root(8)
+==================
+
+NAME
+----
+btrfs-find-root - filter to find btrfs root
+
+SYNOPSIS
+--------
+*btrfs-find-root* [options] <dev>
+
+DESCRIPTION
+-----------
+*btrfs-find-root* is used to find the satisfied root, you can filter by
+root tree's objectid, generation, level.
+
+OPTIONS
+-------
+-a::
+Search through all the metadata extents, even the root is already found.
+-g <generation>::
+Filter root tree by it's original transaction id, tree root's generation in default.
+-o <objectid>::
+Filter root tree by it's objectid,tree root's objectid in default.
+-l <level>::
+Filter root tree by B-+ tree's level, level 0 in default.
+
+EXIT STATUS
+-----------
+*btrfs-find-root* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-find-root.txt b/Documentation/btrfs-find-root.txt
deleted file mode 100644
index e04cd3e8..00000000
--- a/Documentation/btrfs-find-root.txt
+++ /dev/null
@@ -1,35 +0,0 @@
-btrfs-find-root(8)
-==================
-
-NAME
-----
-btrfs-find-root - filter to find btrfs root
-
-SYNOPSIS
---------
-*btrfs-find-root* [options] <dev>
-
-DESCRIPTION
------------
-*btrfs-find-root* is used to find the satisfied root, you can filter by
-root tree's objectid, generation, level.
-
-OPTIONS
--------
--a::
-Search through all the metadata extents, even the root is already found.
--g <generation>::
-Filter root tree by it's original transaction id, tree root's generation in default.
--o <objectid>::
-Filter root tree by it's objectid,tree root's objectid in default.
--l <level>::
-Filter root tree by B-+ tree's level, level 0 in default.
-
-EXIT STATUS
------------
-*btrfs-find-root* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-image.asciidoc b/Documentation/btrfs-image.asciidoc
new file mode 100644
index 00000000..38265171
--- /dev/null
+++ b/Documentation/btrfs-image.asciidoc
@@ -0,0 +1,66 @@
+btrfs-image(8)
+==============
+
+NAME
+----
+btrfs-image - create/restore an image of the filesystem
+
+SYNOPSIS
+--------
+*btrfs-image* [options] <source> <target>
+
+DESCRIPTION
+-----------
+*btrfs-image* is used to create an image of a btrfs filesystem.
+All data will be zeroed, but metadata and the like is preserved.
+Mainly used for debugging purposes.
+
+In the dump mode, source is the btrfs device/file and target is the output
+file (use '-' for stdout).
+
+In the restore mode (option -r), source is the dumped image and target is the btrfs device/file.
+
+
+OPTIONS
+-------
+-r::
+Restore metadump image. By default, this fixes super's chunk tree, by
+using 1 stripe pointing to primary device, so that file system can be
+restored by running tree log reply if possible. To restore without
+changing number of stripes in chunk tree check -o option.
+
+-c <value>::
+Compression level (0 ~ 9).
+
+-t <value>::
+Number of threads (1 ~ 32) to be used to process the image dump or restore.
+
+-o::
+Use the old restore method, this does not fixup the chunk tree so the restored
+file system will not be able to be mounted.
+
+-s::
+Sanitize the file names when generating the image. One -s means just
+generate random garbage, which means that the directory indexes won't match up
+since the hashes won't match with the garbage filenames. Using -ss will
+calculate a collision for the filename so that the hashes match, and if it
+can't calculate a collision then it will just generate garbage.  The collision
+calculator is very time and CPU intensive so only use it if you are having
+problems with your file system tree and need to have it mostly working.
+
+-w::
+Walk all the trees manually and copy any blocks that are referenced. Use this
+option if your extent tree is corrupted to make sure that all of the metadata is
+captured.
+
+-m::
+Restore for multiple devices, more than 1 device should be provided.
+
+EXIT STATUS
+-----------
+*btrfs-image* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-image.txt b/Documentation/btrfs-image.txt
deleted file mode 100644
index 38265171..00000000
--- a/Documentation/btrfs-image.txt
+++ /dev/null
@@ -1,66 +0,0 @@
-btrfs-image(8)
-==============
-
-NAME
-----
-btrfs-image - create/restore an image of the filesystem
-
-SYNOPSIS
---------
-*btrfs-image* [options] <source> <target>
-
-DESCRIPTION
------------
-*btrfs-image* is used to create an image of a btrfs filesystem.
-All data will be zeroed, but metadata and the like is preserved.
-Mainly used for debugging purposes.
-
-In the dump mode, source is the btrfs device/file and target is the output
-file (use '-' for stdout).
-
-In the restore mode (option -r), source is the dumped image and target is the btrfs device/file.
-
-
-OPTIONS
--------
--r::
-Restore metadump image. By default, this fixes super's chunk tree, by
-using 1 stripe pointing to primary device, so that file system can be
-restored by running tree log reply if possible. To restore without
-changing number of stripes in chunk tree check -o option.
-
--c <value>::
-Compression level (0 ~ 9).
-
--t <value>::
-Number of threads (1 ~ 32) to be used to process the image dump or restore.
-
--o::
-Use the old restore method, this does not fixup the chunk tree so the restored
-file system will not be able to be mounted.
-
--s::
-Sanitize the file names when generating the image. One -s means just
-generate random garbage, which means that the directory indexes won't match up
-since the hashes won't match with the garbage filenames. Using -ss will
-calculate a collision for the filename so that the hashes match, and if it
-can't calculate a collision then it will just generate garbage.  The collision
-calculator is very time and CPU intensive so only use it if you are having
-problems with your file system tree and need to have it mostly working.
-
--w::
-Walk all the trees manually and copy any blocks that are referenced. Use this
-option if your extent tree is corrupted to make sure that all of the metadata is
-captured.
-
--m::
-Restore for multiple devices, more than 1 device should be provided.
-
-EXIT STATUS
------------
-*btrfs-image* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-inspect-internal.asciidoc b/Documentation/btrfs-inspect-internal.asciidoc
new file mode 100644
index 00000000..9f6ffac8
--- /dev/null
+++ b/Documentation/btrfs-inspect-internal.asciidoc
@@ -0,0 +1,67 @@
+btrfs-inspect-internal(8)
+=========================
+
+NAME
+----
+btrfs-inspect-internal - resolve different btrfs items for debug purpose
+
+SYNOPSIS
+--------
+*btrfs inspect-internal* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs inspect-internal* is used to resolve different items for debug purpose.
+
+SUBCOMMAND
+----------
+*inode-resolve* [-v] <inode> <path>::
+Resolves an <inode> in subvolume <path> to all filesystem paths.
++
+`Options`
++
+-v::::
+verbose mode. print count of returned paths and ioctl() return value
+
+*logical-resolve* [-Pv] [-s <bufsize>] <logical> <path>::
+Resolves a <logical> address in the filesystem mounted at <path> to all inodes.
++
+By default, each inode is then resolved to a file system path (similar to the
+inode-resolve subcommand).
++
+`Options`
++
+-P::::
+skip the path resolving and print the inodes instead
+-v::::
+verbose mode. print count of returned paths and all ioctl() return values
+-s <bufsize>::::
+set inode container's size.
++
+This is used to increase inode container's size in case it is
+not enough to read all the resolved results. The max value one can set is 64k.
+
+*rootid* <path>::
+For a given file or directory, return the containing tree root id. For a
+subvolume return it's own tree id.
++
+The result is undefined for the so-called empty subvolumes (identified by inode number 2).
+
+*subvolid-resolve* <subvolid> <path>::
+Get file system paths for the given subvolume ID.
+
+EXIT STATUS
+-----------
+*btrfs inspect-internal* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-debug-tree`(8)
diff --git a/Documentation/btrfs-inspect-internal.txt b/Documentation/btrfs-inspect-internal.txt
deleted file mode 100644
index 9f6ffac8..00000000
--- a/Documentation/btrfs-inspect-internal.txt
+++ /dev/null
@@ -1,67 +0,0 @@
-btrfs-inspect-internal(8)
-=========================
-
-NAME
-----
-btrfs-inspect-internal - resolve different btrfs items for debug purpose
-
-SYNOPSIS
---------
-*btrfs inspect-internal* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs inspect-internal* is used to resolve different items for debug purpose.
-
-SUBCOMMAND
-----------
-*inode-resolve* [-v] <inode> <path>::
-Resolves an <inode> in subvolume <path> to all filesystem paths.
-+
-`Options`
-+
--v::::
-verbose mode. print count of returned paths and ioctl() return value
-
-*logical-resolve* [-Pv] [-s <bufsize>] <logical> <path>::
-Resolves a <logical> address in the filesystem mounted at <path> to all inodes.
-+
-By default, each inode is then resolved to a file system path (similar to the
-inode-resolve subcommand).
-+
-`Options`
-+
--P::::
-skip the path resolving and print the inodes instead
--v::::
-verbose mode. print count of returned paths and all ioctl() return values
--s <bufsize>::::
-set inode container's size.
-+
-This is used to increase inode container's size in case it is
-not enough to read all the resolved results. The max value one can set is 64k.
-
-*rootid* <path>::
-For a given file or directory, return the containing tree root id. For a
-subvolume return it's own tree id.
-+
-The result is undefined for the so-called empty subvolumes (identified by inode number 2).
-
-*subvolid-resolve* <subvolid> <path>::
-Get file system paths for the given subvolume ID.
-
-EXIT STATUS
------------
-*btrfs inspect-internal* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-debug-tree`(8)
diff --git a/Documentation/btrfs-map-logical.asciidoc b/Documentation/btrfs-map-logical.asciidoc
new file mode 100644
index 00000000..a3d110cb
--- /dev/null
+++ b/Documentation/btrfs-map-logical.asciidoc
@@ -0,0 +1,37 @@
+btrfs-map-logical(8)
+====================
+
+NAME
+----
+btrfs-map-logical - map btrfs logical extent to physical extent
+
+SYNOPSIS
+--------
+*btrfs-map-logical* <options> <device>
+
+DESCRIPTION
+-----------
+*btrfs-map-logical* can be used to find out what the physical offsets are
+on the mirrors, the result is dumped into stdout in default.
+
+Mainly used for debug purpose.
+
+OPTIONS
+-------
+-l|--logical <logical_num>::
+Logical extent to map.
+-c|--copy <copy>::
+Copy of the extent to read(usually 1 or 2).
+-o|--output <filename>::
+Output file to hold the extent.
+-b|--bytes <bytes>::
+Number of bytes to read.
+
+EXIT STATUS
+-----------
+*btrfs-map-logical* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-map-logical.txt b/Documentation/btrfs-map-logical.txt
deleted file mode 100644
index a3d110cb..00000000
--- a/Documentation/btrfs-map-logical.txt
+++ /dev/null
@@ -1,37 +0,0 @@
-btrfs-map-logical(8)
-====================
-
-NAME
-----
-btrfs-map-logical - map btrfs logical extent to physical extent
-
-SYNOPSIS
---------
-*btrfs-map-logical* <options> <device>
-
-DESCRIPTION
------------
-*btrfs-map-logical* can be used to find out what the physical offsets are
-on the mirrors, the result is dumped into stdout in default.
-
-Mainly used for debug purpose.
-
-OPTIONS
--------
--l|--logical <logical_num>::
-Logical extent to map.
--c|--copy <copy>::
-Copy of the extent to read(usually 1 or 2).
--o|--output <filename>::
-Output file to hold the extent.
--b|--bytes <bytes>::
-Number of bytes to read.
-
-EXIT STATUS
------------
-*btrfs-map-logical* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-mount.asciidoc b/Documentation/btrfs-mount.asciidoc
new file mode 100644
index 00000000..8cf7a0bc
--- /dev/null
+++ b/Documentation/btrfs-mount.asciidoc
@@ -0,0 +1,213 @@
+btrfs-mount(5)
+==============
+
+NAME
+----
+btrfs-mount - mount options and supported file attributes for the btrfs filesystem
+
+DESCRIPTION
+-----------
+This document describes mount options specific to the btrfs filesystem.
+Other generic mount options are available,and are described in the
+`mount`(8) manpage.
+
+MOUNT OPTIONS
+-------------
+*alloc_start='bytes'*::
+	Debugging option to force all block allocations above a certain
+	byte threshold on each block device.  The value is specified in
+	bytes, optionally with a K, M, or G suffix, case insensitive.
+	Default is 1MB.
+
+*autodefrag*::
+	Disable/enable auto defragmentation.
+	Auto defragmentation detects small random writes into files and queue
+	them up for the defrag process.  Works best for small files;
+	Not well suited for large database workloads.
+
+*check_int*|*check_int_data*|*check_int_print_mask='value'*::
+	These debugging options control the behavior of the integrity checking
+	module (the BTRFS_FS_CHECK_INTEGRITY config option required). +
+	+
+	`check_int` enables the integrity checker module, which examines all
+	block write requests to ensure on-disk consistency, at a large
+	memory and CPU cost. +
+	+
+	`check_int_data` includes extent data in the integrity checks, and
+	implies the check_int option. +
+	+
+	`check_int_print_mask` takes a bitmask of BTRFSIC_PRINT_MASK_* values
+	as defined in 'fs/btrfs/check-integrity.c', to control the integrity
+	checker module behavior. +
+	+
+	See comments at the top of 'fs/btrfs/check-integrity.c'
+	for more info.
+
+*commit='seconds'*::
+	Set the interval of periodic commit, 30 seconds by default. Higher
+	values defer data being synced to permanent storage with obvious
+	consequences when the system crashes. The upper bound is not forced,
+	but a warning is printed if it's more than 300 seconds (5 minutes).
+
+*compress*|*compress='type'*|*compress-force*|*compress-force='type'*::
+	Control BTRFS file data compression.  Type may be specified as "zlib"
+	"lzo" or "no" (for no compression, used for remounting).  If no type
+	is specified, zlib is used.  If compress-force is specified,
+	all files will be compressed, whether or not they compress well.
+	If compression is enabled, nodatacow and nodatasum are disabled.
+
+*degraded*::
+	Allow mounts to continue with missing devices.  A read-write mount may
+	fail with too many devices missing, for example if a stripe member
+	is completely missing.
+
+*device='devicepath'*::
+	Specify a device during mount so that ioctls on the control device
+	can be avoided.  Especially useful when trying to mount a multi-device
+	setup as root.  May be specified multiple times for multiple devices.
+
+*discard*::
+	Disable/enable discard mount option.
+	Discard issues frequent commands to let the block device reclaim space
+	freed by the filesystem.
+	This is useful for SSD devices, thinly provisioned
+	LUNs and virtual machine images, but may have a significant
+	performance impact.  (The fstrim command is also available to
+	initiate batch trims from userspace).
+
+*enospc_debug*::
+	Disable/enable debugging option to be more verbose in some ENOSPC conditions.
+
+*fatal_errors='action'*::
+	Action to take when encountering a fatal error. +
+		"bug" - BUG() on a fatal error.  This is the default. +
+		"panic" - panic() on a fatal error.
+
+*flushoncommit*::
+	The `flushoncommit` mount option forces any data dirtied by a write in a
+	prior transaction to commit as part of the current commit.  This makes
+	the committed state a fully consistent view of the file system from the
+	application's perspective (i.e., it includes all completed file system
+	operations).  This was previously the behavior only when a snapshot is
+	created.
+
+*inode_cache*::
+	Enable free inode number caching.   Defaults to off due to an overflow
+	problem when the free space crcs don't fit inside a single page.
+
+*max_inline='bytes'*::
+	Specify the maximum amount of space, in bytes, that can be inlined in
+	a metadata B-tree leaf.  The value is specified in bytes, optionally
+	with a K, M, or G suffix, case insensitive.  In practice, this value
+	is limited by the root sector size, with some space unavailable due
+	to leaf headers.  For a 4k sectorsize, max inline data is ~3900 bytes.
+
+*metadata_ratio='value'*::
+	Specify that 1 metadata chunk should be allocated after every
+	'value' data chunks.  Off by default.
+
+*noacl*::
+	Enable/disable support for Posix Access Control Lists (ACLs).  See the
+	`acl`(5) manual page for more information about ACLs.
+
+*nobarrier*::
+	ensure that certain IOs make it through the device cache and are on
+	persistent storage. If disabled on a device with a volatile
+	(non-battery-backed) write-back cache, nobarrier option will lead to
+	filesystem corruption on a system crash or power loss.
+
+*nodatacow*::
+	Enable/disable data copy-on-write for newly created files.
+	Nodatacow implies nodatasum, and disables all compression.
+
+*nodatasum*::
+	Enable/disable data checksumming for newly created files.
+	Datasum implies datacow.
+
+*notreelog*::
+	Enable/disable the tree logging used for fsync and O_SYNC writes.
+
+*recovery*::
+	Enable autorecovery attempts if a bad tree root is found at mount time.
+	Currently this scans a list of several previous tree roots and tries to
+	use the first readable.
+
+*rescan_uuid_tree*::
+	Force check and rebuild procedure of the UUID tree. This should not
+	normally be needed.
+
+*skip_balance*::
+	Skip automatic resume of interrupted balance operation after mount.
+	May be resumed with "btrfs balance resume."
+
+*nospace_cache*::
+	Disable freespace cache loading without clearing the cache.
+
+*clear_cache*::
+	Force clearing and rebuilding of the disk space cache if something
+	has gone wrong.
+
+*ssd*|*nossd*|*ssd_spread*::
+	Options to control ssd allocation schemes.  By default, BTRFS will
+	enable or disable ssd allocation heuristics depending on whether a
+	rotational or nonrotational disk is in use.  The ssd and nossd options
+	can override this autodetection. +
+	The ssd_spread mount option attempts to allocate into big chunks
+	of unused space, and may perform better on low-end ssds.  ssd_spread
+	implies ssd, enabling all other ssd heuristics as well.
+
+*subvol='path'*::
+	Mount subvolume at 'path' rather than the root subvolume. The
+	'path' is relative to the top level subvolume.
+
+*subvolid='ID'*::
+	Mount subvolume specified by an ID number rather than the root subvolume.
+	This allows mounting of subvolumes which are not in the root of the mounted
+	filesystem.
+	You can use "btrfs subvolume list" to see subvolume ID numbers.
+
+*subvolrootid='objectid' (deprecated)*::
+	Mount subvolume specified by 'objectid' rather than the root subvolume.
+	This allows mounting of subvolumes which are not in the root of the mounted
+	filesystem.
+	You can use "btrfs subvolume show" to see the object ID for a subvolume.
+
+*thread_pool='number'*::
+	The number of worker threads to allocate.  The default number is equal
+	to the number of CPUs + 2, or 8, whichever is smaller.
+
+*user_subvol_rm_allowed*::
+	Allow subvolumes to be deleted by a non-root user. Use with caution.
+
+FILE ATTRIBUTES
+---------------
+The btrfs filesystem supports setting the following file
+attributes the `chattr`(1) utility
+
+*a* -- append only
+
+*A* -- no atime updates
+
+*c* -- compressed
+
+*C* -- no copy on write
+
+*d* -- no dump
+
+*D* -- synchronous directory updates
+
+*i* -- immutable
+
+*S* -- synchronous updates
+
+*X* -- no compression
+
+For descriptions of these attribute flags, please refer to the
+`chattr`(1) man page.
+
+SEE ALSO
+--------
+`chattr`(1),
+`mkfs.btrfs`(8),
+`mount`(8),
+`btrfs`(8)
diff --git a/Documentation/btrfs-mount.txt b/Documentation/btrfs-mount.txt
deleted file mode 100644
index 8cf7a0bc..00000000
--- a/Documentation/btrfs-mount.txt
+++ /dev/null
@@ -1,213 +0,0 @@
-btrfs-mount(5)
-==============
-
-NAME
-----
-btrfs-mount - mount options and supported file attributes for the btrfs filesystem
-
-DESCRIPTION
------------
-This document describes mount options specific to the btrfs filesystem.
-Other generic mount options are available,and are described in the
-`mount`(8) manpage.
-
-MOUNT OPTIONS
--------------
-*alloc_start='bytes'*::
-	Debugging option to force all block allocations above a certain
-	byte threshold on each block device.  The value is specified in
-	bytes, optionally with a K, M, or G suffix, case insensitive.
-	Default is 1MB.
-
-*autodefrag*::
-	Disable/enable auto defragmentation.
-	Auto defragmentation detects small random writes into files and queue
-	them up for the defrag process.  Works best for small files;
-	Not well suited for large database workloads.
-
-*check_int*|*check_int_data*|*check_int_print_mask='value'*::
-	These debugging options control the behavior of the integrity checking
-	module (the BTRFS_FS_CHECK_INTEGRITY config option required). +
-	+
-	`check_int` enables the integrity checker module, which examines all
-	block write requests to ensure on-disk consistency, at a large
-	memory and CPU cost. +
-	+
-	`check_int_data` includes extent data in the integrity checks, and
-	implies the check_int option. +
-	+
-	`check_int_print_mask` takes a bitmask of BTRFSIC_PRINT_MASK_* values
-	as defined in 'fs/btrfs/check-integrity.c', to control the integrity
-	checker module behavior. +
-	+
-	See comments at the top of 'fs/btrfs/check-integrity.c'
-	for more info.
-
-*commit='seconds'*::
-	Set the interval of periodic commit, 30 seconds by default. Higher
-	values defer data being synced to permanent storage with obvious
-	consequences when the system crashes. The upper bound is not forced,
-	but a warning is printed if it's more than 300 seconds (5 minutes).
-
-*compress*|*compress='type'*|*compress-force*|*compress-force='type'*::
-	Control BTRFS file data compression.  Type may be specified as "zlib"
-	"lzo" or "no" (for no compression, used for remounting).  If no type
-	is specified, zlib is used.  If compress-force is specified,
-	all files will be compressed, whether or not they compress well.
-	If compression is enabled, nodatacow and nodatasum are disabled.
-
-*degraded*::
-	Allow mounts to continue with missing devices.  A read-write mount may
-	fail with too many devices missing, for example if a stripe member
-	is completely missing.
-
-*device='devicepath'*::
-	Specify a device during mount so that ioctls on the control device
-	can be avoided.  Especially useful when trying to mount a multi-device
-	setup as root.  May be specified multiple times for multiple devices.
-
-*discard*::
-	Disable/enable discard mount option.
-	Discard issues frequent commands to let the block device reclaim space
-	freed by the filesystem.
-	This is useful for SSD devices, thinly provisioned
-	LUNs and virtual machine images, but may have a significant
-	performance impact.  (The fstrim command is also available to
-	initiate batch trims from userspace).
-
-*enospc_debug*::
-	Disable/enable debugging option to be more verbose in some ENOSPC conditions.
-
-*fatal_errors='action'*::
-	Action to take when encountering a fatal error. +
-		"bug" - BUG() on a fatal error.  This is the default. +
-		"panic" - panic() on a fatal error.
-
-*flushoncommit*::
-	The `flushoncommit` mount option forces any data dirtied by a write in a
-	prior transaction to commit as part of the current commit.  This makes
-	the committed state a fully consistent view of the file system from the
-	application's perspective (i.e., it includes all completed file system
-	operations).  This was previously the behavior only when a snapshot is
-	created.
-
-*inode_cache*::
-	Enable free inode number caching.   Defaults to off due to an overflow
-	problem when the free space crcs don't fit inside a single page.
-
-*max_inline='bytes'*::
-	Specify the maximum amount of space, in bytes, that can be inlined in
-	a metadata B-tree leaf.  The value is specified in bytes, optionally
-	with a K, M, or G suffix, case insensitive.  In practice, this value
-	is limited by the root sector size, with some space unavailable due
-	to leaf headers.  For a 4k sectorsize, max inline data is ~3900 bytes.
-
-*metadata_ratio='value'*::
-	Specify that 1 metadata chunk should be allocated after every
-	'value' data chunks.  Off by default.
-
-*noacl*::
-	Enable/disable support for Posix Access Control Lists (ACLs).  See the
-	`acl`(5) manual page for more information about ACLs.
-
-*nobarrier*::
-	ensure that certain IOs make it through the device cache and are on
-	persistent storage. If disabled on a device with a volatile
-	(non-battery-backed) write-back cache, nobarrier option will lead to
-	filesystem corruption on a system crash or power loss.
-
-*nodatacow*::
-	Enable/disable data copy-on-write for newly created files.
-	Nodatacow implies nodatasum, and disables all compression.
-
-*nodatasum*::
-	Enable/disable data checksumming for newly created files.
-	Datasum implies datacow.
-
-*notreelog*::
-	Enable/disable the tree logging used for fsync and O_SYNC writes.
-
-*recovery*::
-	Enable autorecovery attempts if a bad tree root is found at mount time.
-	Currently this scans a list of several previous tree roots and tries to
-	use the first readable.
-
-*rescan_uuid_tree*::
-	Force check and rebuild procedure of the UUID tree. This should not
-	normally be needed.
-
-*skip_balance*::
-	Skip automatic resume of interrupted balance operation after mount.
-	May be resumed with "btrfs balance resume."
-
-*nospace_cache*::
-	Disable freespace cache loading without clearing the cache.
-
-*clear_cache*::
-	Force clearing and rebuilding of the disk space cache if something
-	has gone wrong.
-
-*ssd*|*nossd*|*ssd_spread*::
-	Options to control ssd allocation schemes.  By default, BTRFS will
-	enable or disable ssd allocation heuristics depending on whether a
-	rotational or nonrotational disk is in use.  The ssd and nossd options
-	can override this autodetection. +
-	The ssd_spread mount option attempts to allocate into big chunks
-	of unused space, and may perform better on low-end ssds.  ssd_spread
-	implies ssd, enabling all other ssd heuristics as well.
-
-*subvol='path'*::
-	Mount subvolume at 'path' rather than the root subvolume. The
-	'path' is relative to the top level subvolume.
-
-*subvolid='ID'*::
-	Mount subvolume specified by an ID number rather than the root subvolume.
-	This allows mounting of subvolumes which are not in the root of the mounted
-	filesystem.
-	You can use "btrfs subvolume list" to see subvolume ID numbers.
-
-*subvolrootid='objectid' (deprecated)*::
-	Mount subvolume specified by 'objectid' rather than the root subvolume.
-	This allows mounting of subvolumes which are not in the root of the mounted
-	filesystem.
-	You can use "btrfs subvolume show" to see the object ID for a subvolume.
-
-*thread_pool='number'*::
-	The number of worker threads to allocate.  The default number is equal
-	to the number of CPUs + 2, or 8, whichever is smaller.
-
-*user_subvol_rm_allowed*::
-	Allow subvolumes to be deleted by a non-root user. Use with caution.
-
-FILE ATTRIBUTES
----------------
-The btrfs filesystem supports setting the following file
-attributes the `chattr`(1) utility
-
-*a* -- append only
-
-*A* -- no atime updates
-
-*c* -- compressed
-
-*C* -- no copy on write
-
-*d* -- no dump
-
-*D* -- synchronous directory updates
-
-*i* -- immutable
-
-*S* -- synchronous updates
-
-*X* -- no compression
-
-For descriptions of these attribute flags, please refer to the
-`chattr`(1) man page.
-
-SEE ALSO
---------
-`chattr`(1),
-`mkfs.btrfs`(8),
-`mount`(8),
-`btrfs`(8)
diff --git a/Documentation/btrfs-property.asciidoc b/Documentation/btrfs-property.asciidoc
new file mode 100644
index 00000000..8b9b7f03
--- /dev/null
+++ b/Documentation/btrfs-property.asciidoc
@@ -0,0 +1,73 @@
+btrfs-property(8)
+=================
+
+NAME
+----
+btrfs-property - get/set/list properties for given btrfs object.
+
+SYNOPSIS
+--------
+*btrfs property* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs property* is used to get/set/list property for given btrfs object.
+See the description of *get* subcommand for more information about
+both btrfs object and property.
+
+*btrfs property* provides an unified and user-friendly method to tune different
+btrfs properties instead of using the traditional method like `chattr`(1) or
+`lsattr`(1).
+
+SUBCOMMAND
+----------
+*get* [-t <type>] <object> [<name>]::
+Gets a property from a btrfs object.
++
+A btrfs object, which is set by <object>, can be a btrfs filesystem
+itself, a btrfs subvolume, an inode(file or directory) inside btrfs,
+or a device on which a btrfs exists.
++
+The '-t <type>' option can be used to explicitly
+specify what type of object you meant. This is only needed when a
+property could be set for more then one object type.
++
+Possible types are 's[ubvol]', 'f[ilesystem]', 'i[node]' and 'd[evice]'.
++
+Set the name of property by '<name>'. If no '<name>' is specified,
+all properties for the given object are printed. '<name>' is one of
+the followings.
+
+ro::::
+read-only flag of subvolume: true or false
+label::::
+label of device
+compression::::
+compression setting for an inode: lzo, zlib, or "" (empty string)
+
+*list* [-t <type>] <object>::
+Lists available properties with their descriptions for the given object.
++
+See the description of *get* subcommand for the meaning of each option.
+
+*set* [-t <type>] <object> <name> <value>::
+Sets a property on a btrfs object.
++
+See the description of *get* subcommand for the meaning of each option.
+
+EXIT STATUS
+-----------
+*btrfs property* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`lsattr`(1),
+`chattr`(1)
diff --git a/Documentation/btrfs-property.txt b/Documentation/btrfs-property.txt
deleted file mode 100644
index 8b9b7f03..00000000
--- a/Documentation/btrfs-property.txt
+++ /dev/null
@@ -1,73 +0,0 @@
-btrfs-property(8)
-=================
-
-NAME
-----
-btrfs-property - get/set/list properties for given btrfs object.
-
-SYNOPSIS
---------
-*btrfs property* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs property* is used to get/set/list property for given btrfs object.
-See the description of *get* subcommand for more information about
-both btrfs object and property.
-
-*btrfs property* provides an unified and user-friendly method to tune different
-btrfs properties instead of using the traditional method like `chattr`(1) or
-`lsattr`(1).
-
-SUBCOMMAND
-----------
-*get* [-t <type>] <object> [<name>]::
-Gets a property from a btrfs object.
-+
-A btrfs object, which is set by <object>, can be a btrfs filesystem
-itself, a btrfs subvolume, an inode(file or directory) inside btrfs,
-or a device on which a btrfs exists.
-+
-The '-t <type>' option can be used to explicitly
-specify what type of object you meant. This is only needed when a
-property could be set for more then one object type.
-+
-Possible types are 's[ubvol]', 'f[ilesystem]', 'i[node]' and 'd[evice]'.
-+
-Set the name of property by '<name>'. If no '<name>' is specified,
-all properties for the given object are printed. '<name>' is one of
-the followings.
-
-ro::::
-read-only flag of subvolume: true or false
-label::::
-label of device
-compression::::
-compression setting for an inode: lzo, zlib, or "" (empty string)
-
-*list* [-t <type>] <object>::
-Lists available properties with their descriptions for the given object.
-+
-See the description of *get* subcommand for the meaning of each option.
-
-*set* [-t <type>] <object> <name> <value>::
-Sets a property on a btrfs object.
-+
-See the description of *get* subcommand for the meaning of each option.
-
-EXIT STATUS
------------
-*btrfs property* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`lsattr`(1),
-`chattr`(1)
diff --git a/Documentation/btrfs-qgroup.asciidoc b/Documentation/btrfs-qgroup.asciidoc
new file mode 100644
index 00000000..eadfe1c9
--- /dev/null
+++ b/Documentation/btrfs-qgroup.asciidoc
@@ -0,0 +1,133 @@
+btrfs-qgroup(8)
+===============
+
+NAME
+----
+btrfs-qgroup - control the quota group of a btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs qgroup* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs qgroup* is used to control quota group(qgroup) of a btrfs filesystem.
+
+NOTE: To use qgroup, it needs to enable quota first using *btrfs quota*
+command.
+
+WARNING: Qgroup is not stable yet and will impact performance in current mainline
+kernel(v3.14 so far).
+
+QGROUP
+------
+Quota group or qgroup in btrfs has its hierarchy like subvolume.
+One subvolume/snapshot can reach its quota limits if it consumes all the quota
+assigned to it or any of the parent qgroup(s).
+
+Also for snapshot, it consumes no quota initially since all its data
+shares with its parent, so only modification in snapshot consumes quota.
+
+Every subvolume/snapshot will have its own qgroup with id '0/<subvolume id>'
+upon creating, but can be later destroyed by *btrfs qgroup destroy* command.
+
+NOTE: If the qgroup of a subvolume is destroyed, quota about the subvolume
+will not be functional until qgroup '0/<subvolume id>' is created again.
+
+SUBCOMMAND
+----------
+*assign* <src> <dst> <path>::
+Assign qgroup <src> as the child qgroup of <dst> in the btrfs filesystem
+identified by <path>.
+
+*create* <qgroupid> <path>::
+Create a subvolume quota group.
++
+For the '0/<subvolume id>' qgroup, a qgroup can be created even before the
+subvolume created.
+
+*destroy* <qgroupid> <path>::
+Destroy a qgroup.
++
+If a qgroup is no isolated,which means it is a parent or child qgroup, it
+can't be destroyed.
+
+*limit* [options] <size>|none [<qgroupid>] <path>::
+Limit the size of a qgroup to <size> or no limit in the btrfs filesystem
+identified by <path>.
++
+If <qgroupid> is not given, qgroup of the subvolume identified by <path>
+is used if possible.
++
+`Options`
++
+-c::::
+limit amount of data after compression. This is the default, it is currently not
+possible to turn off this option.
++
+-e::::
+limit space exclusively assigned to this qgroup.
+
+*remove* <src> <dst> <path>::
+Remove the relationship between child qgroup <src> and parent qgroup <dst> in
+the btrfs filesystem identified by <path>.
+
+*show* [options] <path>::
+Show all qgroups in the btrfs filesystem identified by <path>.
++
+`Options`
++
+-p::::
+print parent qgroup id.
+-c::::
+print child qgroup id.
+-r::::
+print limit of referenced size of qgroup.
+-e::::
+print limit of exclusive size of qgroup.
+-F::::
+list all qgroups which impact the given path(include ancestral qgroups)
+-f::::
+list all qgroups which impact the given path(exclude ancestral qgroups)
+--raw::::
+raw numbers in bytes, without the 'B' suffix.
+--human-readable::::
+print human friendly numbers, base 1024, this is the default
+--iec::::
+select the 1024 base for the following options, according to the IEC standard.
+--si::::
+select the 1000 base for the following options, according to the SI standard.
+--kbytes::::
+show sizes in KiB, or kB with --si.
+--mbytes::::
+show sizes in MiB, or MB with --si.
+--gbytes::::
+show sizes in GiB, or GB with --si.
+--tbytes::::
+show sizes in TiB, or TB with --si.
+--sort=[\+/-]<attr>[,[+/-]<attr>]...::::
+list qgroups in order of <attr>.
++
+<attr> can be one or more of qgroupid,rfer,excl,max_rfer,max_excl.
++
+Prefix \'+' means ascending order and \'-' means descending order of <attr>.
+If no prefix is given, use ascending order by default.
++
+If multiple <attr>s is given, use comma to separate.
+
+EXIT STATUS
+-----------
+*btrfs qgroup* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-subvolume`(8),
+`btrfs-quota`(8),
diff --git a/Documentation/btrfs-qgroup.txt b/Documentation/btrfs-qgroup.txt
deleted file mode 100644
index eadfe1c9..00000000
--- a/Documentation/btrfs-qgroup.txt
+++ /dev/null
@@ -1,133 +0,0 @@
-btrfs-qgroup(8)
-===============
-
-NAME
-----
-btrfs-qgroup - control the quota group of a btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs qgroup* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs qgroup* is used to control quota group(qgroup) of a btrfs filesystem.
-
-NOTE: To use qgroup, it needs to enable quota first using *btrfs quota*
-command.
-
-WARNING: Qgroup is not stable yet and will impact performance in current mainline
-kernel(v3.14 so far).
-
-QGROUP
-------
-Quota group or qgroup in btrfs has its hierarchy like subvolume.
-One subvolume/snapshot can reach its quota limits if it consumes all the quota
-assigned to it or any of the parent qgroup(s).
-
-Also for snapshot, it consumes no quota initially since all its data
-shares with its parent, so only modification in snapshot consumes quota.
-
-Every subvolume/snapshot will have its own qgroup with id '0/<subvolume id>'
-upon creating, but can be later destroyed by *btrfs qgroup destroy* command.
-
-NOTE: If the qgroup of a subvolume is destroyed, quota about the subvolume
-will not be functional until qgroup '0/<subvolume id>' is created again.
-
-SUBCOMMAND
-----------
-*assign* <src> <dst> <path>::
-Assign qgroup <src> as the child qgroup of <dst> in the btrfs filesystem
-identified by <path>.
-
-*create* <qgroupid> <path>::
-Create a subvolume quota group.
-+
-For the '0/<subvolume id>' qgroup, a qgroup can be created even before the
-subvolume created.
-
-*destroy* <qgroupid> <path>::
-Destroy a qgroup.
-+
-If a qgroup is no isolated,which means it is a parent or child qgroup, it
-can't be destroyed.
-
-*limit* [options] <size>|none [<qgroupid>] <path>::
-Limit the size of a qgroup to <size> or no limit in the btrfs filesystem
-identified by <path>.
-+
-If <qgroupid> is not given, qgroup of the subvolume identified by <path>
-is used if possible.
-+
-`Options`
-+
--c::::
-limit amount of data after compression. This is the default, it is currently not
-possible to turn off this option.
-+
--e::::
-limit space exclusively assigned to this qgroup.
-
-*remove* <src> <dst> <path>::
-Remove the relationship between child qgroup <src> and parent qgroup <dst> in
-the btrfs filesystem identified by <path>.
-
-*show* [options] <path>::
-Show all qgroups in the btrfs filesystem identified by <path>.
-+
-`Options`
-+
--p::::
-print parent qgroup id.
--c::::
-print child qgroup id.
--r::::
-print limit of referenced size of qgroup.
--e::::
-print limit of exclusive size of qgroup.
--F::::
-list all qgroups which impact the given path(include ancestral qgroups)
--f::::
-list all qgroups which impact the given path(exclude ancestral qgroups)
---raw::::
-raw numbers in bytes, without the 'B' suffix.
---human-readable::::
-print human friendly numbers, base 1024, this is the default
---iec::::
-select the 1024 base for the following options, according to the IEC standard.
---si::::
-select the 1000 base for the following options, according to the SI standard.
---kbytes::::
-show sizes in KiB, or kB with --si.
---mbytes::::
-show sizes in MiB, or MB with --si.
---gbytes::::
-show sizes in GiB, or GB with --si.
---tbytes::::
-show sizes in TiB, or TB with --si.
---sort=[\+/-]<attr>[,[+/-]<attr>]...::::
-list qgroups in order of <attr>.
-+
-<attr> can be one or more of qgroupid,rfer,excl,max_rfer,max_excl.
-+
-Prefix \'+' means ascending order and \'-' means descending order of <attr>.
-If no prefix is given, use ascending order by default.
-+
-If multiple <attr>s is given, use comma to separate.
-
-EXIT STATUS
------------
-*btrfs qgroup* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-subvolume`(8),
-`btrfs-quota`(8),
diff --git a/Documentation/btrfs-quota.asciidoc b/Documentation/btrfs-quota.asciidoc
new file mode 100644
index 00000000..00e09c61
--- /dev/null
+++ b/Documentation/btrfs-quota.asciidoc
@@ -0,0 +1,56 @@
+btrfs-quota(8)
+==============
+
+NAME
+----
+btrfs-quota - control the quota of a btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs quota* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs quota* is used to enable/disable or rescan subvolume quota of a btrfs
+filesystem.
+
+For setting quota or other quota operations on a btrfs filesystem, please see
+`btrfs-qgroup`(8) for details.
+
+WARNING: Quota and qgroup in btrfs filesystem is not stable and impacts
+performance in mainline kernel yet(v3.14 so far).
+
+SUBCOMMAND
+----------
+*disable* <path>::
+Disable subvolume quota support for a filesystem.
+
+*enable* <path>::
+Enable subvolume quota support for a filesystem.
+
+*rescan* [-s] <path>::
+Trash all qgroup numbers and scan the metadata again with the current config.
++
+`Options`
++
+-s::::
+show status of a running rescan operation.
+-w::::
+wait for rescan operation to finish(can be already in progress).
+
+EXIT STATUS
+-----------
+*btrfs quota* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-subvolume`(8),
+`btrfs-qgroup`(8)
diff --git a/Documentation/btrfs-quota.txt b/Documentation/btrfs-quota.txt
deleted file mode 100644
index 00e09c61..00000000
--- a/Documentation/btrfs-quota.txt
+++ /dev/null
@@ -1,56 +0,0 @@
-btrfs-quota(8)
-==============
-
-NAME
-----
-btrfs-quota - control the quota of a btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs quota* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs quota* is used to enable/disable or rescan subvolume quota of a btrfs
-filesystem.
-
-For setting quota or other quota operations on a btrfs filesystem, please see
-`btrfs-qgroup`(8) for details.
-
-WARNING: Quota and qgroup in btrfs filesystem is not stable and impacts
-performance in mainline kernel yet(v3.14 so far).
-
-SUBCOMMAND
-----------
-*disable* <path>::
-Disable subvolume quota support for a filesystem.
-
-*enable* <path>::
-Enable subvolume quota support for a filesystem.
-
-*rescan* [-s] <path>::
-Trash all qgroup numbers and scan the metadata again with the current config.
-+
-`Options`
-+
--s::::
-show status of a running rescan operation.
--w::::
-wait for rescan operation to finish(can be already in progress).
-
-EXIT STATUS
------------
-*btrfs quota* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-subvolume`(8),
-`btrfs-qgroup`(8)
diff --git a/Documentation/btrfs-receive.asciidoc b/Documentation/btrfs-receive.asciidoc
new file mode 100644
index 00000000..ed1e247f
--- /dev/null
+++ b/Documentation/btrfs-receive.asciidoc
@@ -0,0 +1,59 @@
+btrfs-receive(8)
+================
+
+NAME
+----
+btrfs-receive - receive subvolumes from stdin/file.
+
+SYNOPSIS
+--------
+*btrfs receive* [-ve] [-f <infile>] [--max-errors <N>] <mount>
+
+DESCRIPTION
+-----------
+Receives one or more subvolumes that were previously
+sent with *btrfs send*. The received subvolumes are stored
+into <mount>.
+
+*btrfs receive* will fail with the following case:
+
+1. a receiving subvolume already exists.
+
+2. a previously received subvolume was changed after it was received.
+
+3. default subvolume is changed or you don't mount btrfs filesystem with
+fs tree.
+
+After receiving a subvolume, it is immediately set to read only.
+
+`Options`
+
+-v::
+Enable verbose debug output. Each occurrence of this option increases the
+verbose level more.
+-f <infile>::
+By default, btrfs receive uses stdin to receive the subvolumes.
+Use this option to specify a file to use instead.
+-e::
+Terminate after receiving an <end cmd> in the data stream.
+Without this option, the receiver terminates only if an error is recognized
+or on EOF.
+--max-errors <N>::
+Terminate as soon as N errors happened while processing commands from the send
+stream. Default value is 1. A value of 0 means no limit.
+
+EXIT STATUS
+-----------
+*btrfs receive* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-send`(8)
diff --git a/Documentation/btrfs-receive.txt b/Documentation/btrfs-receive.txt
deleted file mode 100644
index ed1e247f..00000000
--- a/Documentation/btrfs-receive.txt
+++ /dev/null
@@ -1,59 +0,0 @@
-btrfs-receive(8)
-================
-
-NAME
-----
-btrfs-receive - receive subvolumes from stdin/file.
-
-SYNOPSIS
---------
-*btrfs receive* [-ve] [-f <infile>] [--max-errors <N>] <mount>
-
-DESCRIPTION
------------
-Receives one or more subvolumes that were previously
-sent with *btrfs send*. The received subvolumes are stored
-into <mount>.
-
-*btrfs receive* will fail with the following case:
-
-1. a receiving subvolume already exists.
-
-2. a previously received subvolume was changed after it was received.
-
-3. default subvolume is changed or you don't mount btrfs filesystem with
-fs tree.
-
-After receiving a subvolume, it is immediately set to read only.
-
-`Options`
-
--v::
-Enable verbose debug output. Each occurrence of this option increases the
-verbose level more.
--f <infile>::
-By default, btrfs receive uses stdin to receive the subvolumes.
-Use this option to specify a file to use instead.
--e::
-Terminate after receiving an <end cmd> in the data stream.
-Without this option, the receiver terminates only if an error is recognized
-or on EOF.
---max-errors <N>::
-Terminate as soon as N errors happened while processing commands from the send
-stream. Default value is 1. A value of 0 means no limit.
-
-EXIT STATUS
------------
-*btrfs receive* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-send`(8)
diff --git a/Documentation/btrfs-replace.asciidoc b/Documentation/btrfs-replace.asciidoc
new file mode 100644
index 00000000..774d8506
--- /dev/null
+++ b/Documentation/btrfs-replace.asciidoc
@@ -0,0 +1,81 @@
+btrfs-replace(8)
+===============
+
+NAME
+----
+btrfs-replace - replace devices managed by btrfs with other device.
+
+SYNOPSIS
+--------
+*btrfs replace* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs replace* is used to replace btrfs managed devices with other device.
+
+NOTE: this is not currently supported for RAID5/6 profiles and must use the
+device add/delete workaround.
+It is recommended to see `btrfs-device`(8) for more details about btrfs device
+management.
+
+SUBCOMMAND
+----------
+*cancel* <mount_point>::
+Cancel a running device replace operation.
+
+*start* [-Bfr] <srcdev>|<devid> <targetdev> <path>::
+Replace device of a btrfs filesystem.
++
+On a live filesystem, duplicate the data to the target device which
+is currently stored on the source device.
+If the source device is not available anymore, or if the -r option is set,
+the data is built only using the RAID redundancy mechanisms.
+After completion of the operation, the source device is removed from the
+filesystem.
+If the <srcdev> is a numerical value, it is assumed to be the device id
+of the filesystem which is mounted at <path>, otherwise is is
+the path to the source device. If the source device is disconnected,
+from the system, you have to use the devid parameter format.
+The <targetdev> needs to be same size or larger than the <srcdev>.
++
+`Options`
++
+-r::::
+only read from <srcdev> if no other zero-defect mirror exists.
+(enable this if your drive has lots of read errors, the access would be very
+slow)
+-f::::
+force using and overwriting <targetdev> even if it looks like
+containing a valid btrfs filesystem.
++
+A valid filesystem is assumed if a btrfs superblock is found which contains a
+correct checksum. Devices which are currently mounted are
+never allowed to be used as the <targetdev>.
++
+-B::::
+no background replace.
+
+*status* [-1] <mount_point>::
+Print status and progress information of a running device replace operation.
++
+`Options`
++
+-1::::
+print once instead of print continuously until the replace
+operation finishes (or is canceled)
+
+EXIT STATUS
+-----------
+*btrfs replace* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-device`(8),
diff --git a/Documentation/btrfs-replace.txt b/Documentation/btrfs-replace.txt
deleted file mode 100644
index 774d8506..00000000
--- a/Documentation/btrfs-replace.txt
+++ /dev/null
@@ -1,81 +0,0 @@
-btrfs-replace(8)
-===============
-
-NAME
-----
-btrfs-replace - replace devices managed by btrfs with other device.
-
-SYNOPSIS
---------
-*btrfs replace* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs replace* is used to replace btrfs managed devices with other device.
-
-NOTE: this is not currently supported for RAID5/6 profiles and must use the
-device add/delete workaround.
-It is recommended to see `btrfs-device`(8) for more details about btrfs device
-management.
-
-SUBCOMMAND
-----------
-*cancel* <mount_point>::
-Cancel a running device replace operation.
-
-*start* [-Bfr] <srcdev>|<devid> <targetdev> <path>::
-Replace device of a btrfs filesystem.
-+
-On a live filesystem, duplicate the data to the target device which
-is currently stored on the source device.
-If the source device is not available anymore, or if the -r option is set,
-the data is built only using the RAID redundancy mechanisms.
-After completion of the operation, the source device is removed from the
-filesystem.
-If the <srcdev> is a numerical value, it is assumed to be the device id
-of the filesystem which is mounted at <path>, otherwise is is
-the path to the source device. If the source device is disconnected,
-from the system, you have to use the devid parameter format.
-The <targetdev> needs to be same size or larger than the <srcdev>.
-+
-`Options`
-+
--r::::
-only read from <srcdev> if no other zero-defect mirror exists.
-(enable this if your drive has lots of read errors, the access would be very
-slow)
--f::::
-force using and overwriting <targetdev> even if it looks like
-containing a valid btrfs filesystem.
-+
-A valid filesystem is assumed if a btrfs superblock is found which contains a
-correct checksum. Devices which are currently mounted are
-never allowed to be used as the <targetdev>.
-+
--B::::
-no background replace.
-
-*status* [-1] <mount_point>::
-Print status and progress information of a running device replace operation.
-+
-`Options`
-+
--1::::
-print once instead of print continuously until the replace
-operation finishes (or is canceled)
-
-EXIT STATUS
------------
-*btrfs replace* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-device`(8),
diff --git a/Documentation/btrfs-rescue.asciidoc b/Documentation/btrfs-rescue.asciidoc
new file mode 100644
index 00000000..e0acf091
--- /dev/null
+++ b/Documentation/btrfs-rescue.asciidoc
@@ -0,0 +1,58 @@
+btrfs-check(8)
+==============
+
+NAME
+----
+btrfs-rescue - Recover a damaged btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs rescue* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs rescue* is used to try to recover a damaged btrfs filesystem.
+
+SUBCOMMAND
+----------
+*chunk-recover* [options] <device>::
+Recover the chunk tree by scanning the devices
++
+`Options`
++
+-y::::
+assume an answer of 'yes' to all questions.
+-v::::
+verbose mode.
+-h::::
+help.
+
+NOTE: Since *chunk-recover* will scan the whole device, it will be *VERY* slow
+especially executed on a large device.
+
+*super-recover* [options] <device>::
+Recover bad superblocks from good copies.
++
+`Options`
++
+-y::::
+assume an answer of 'yes' to all questions.
+-v::::
+verbose mode.
+
+EXIT STATUS
+-----------
+*btrfs rescue* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-scrub`(8),
+`btrfs-check`(8)
diff --git a/Documentation/btrfs-rescue.txt b/Documentation/btrfs-rescue.txt
deleted file mode 100644
index e0acf091..00000000
--- a/Documentation/btrfs-rescue.txt
+++ /dev/null
@@ -1,58 +0,0 @@
-btrfs-check(8)
-==============
-
-NAME
-----
-btrfs-rescue - Recover a damaged btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs rescue* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs rescue* is used to try to recover a damaged btrfs filesystem.
-
-SUBCOMMAND
-----------
-*chunk-recover* [options] <device>::
-Recover the chunk tree by scanning the devices
-+
-`Options`
-+
--y::::
-assume an answer of 'yes' to all questions.
--v::::
-verbose mode.
--h::::
-help.
-
-NOTE: Since *chunk-recover* will scan the whole device, it will be *VERY* slow
-especially executed on a large device.
-
-*super-recover* [options] <device>::
-Recover bad superblocks from good copies.
-+
-`Options`
-+
--y::::
-assume an answer of 'yes' to all questions.
--v::::
-verbose mode.
-
-EXIT STATUS
------------
-*btrfs rescue* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-scrub`(8),
-`btrfs-check`(8)
diff --git a/Documentation/btrfs-restore.asciidoc b/Documentation/btrfs-restore.asciidoc
new file mode 100644
index 00000000..20fc366a
--- /dev/null
+++ b/Documentation/btrfs-restore.asciidoc
@@ -0,0 +1,85 @@
+btrfs-restore(8)
+================
+
+NAME
+----
+btrfs-restore - try to restore files from a damaged btrfs filesystem(unmounted)
+
+SYNOPSIS
+--------
+*btrfs restore* [options] <device> <path> | -l <device>
+
+DESCRIPTION
+-----------
+*btrfs restore* is used to try to salvage files from a damaged filesystem and
+restore them into <path> or just list the tree roots.
+
+Since current `btrfs-check`(8) or `btrfs-rescue`(8) only has very limited usage,
+*btrfs restore* is normally a better choice.
+
+NOTE: It is recommended to read the following btrfs wiki page if your data is
+not salvaged with default option: +
+https://btrfs.wiki.kernel.org/index.php/Restore
+
+OPTIONS
+-------
+-s::
+get snapshots, btrfs restore skips snapshots in default.
+
+-x::
+get extended attributes.
+
+-v::
+verbose.
+
+-i::
+ignore errors.
+
+-o::
+overwrite directories/files in <path>.
+
+-t <bytenr>::
+use <bytenr> to read root tree.
+
+-f <bytenr>::
+only restore files that are under specified root whose root bytenr is <bytenr>.
+
+-u <mirror>::
+use given superblock mirror identified by <mirror>, it can be 0,1,2.
+
+-r <rootid>::
+only restore files that are under specified root whose objectid is <rootid>.
+
+-d::
+find dir.
+
+-l::
+list tree roots.
+
+-D|--dry-run::
+dry run (only list files that would be recovered).
+
+--path-regex <regex>::
+restore only filenames matching regex, you have to use following syntax (possibly quoted):
++
++^/(|home(|/username(|/Desktop(|/.*))))$+
+
+-c::
+ignore case (--path-regrex only).
+
+EXIT STATUS
+-----------
+*btrfs restore* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-rescue`(8),
+`btrfs-check`(8)
diff --git a/Documentation/btrfs-restore.txt b/Documentation/btrfs-restore.txt
deleted file mode 100644
index 20fc366a..00000000
--- a/Documentation/btrfs-restore.txt
+++ /dev/null
@@ -1,85 +0,0 @@
-btrfs-restore(8)
-================
-
-NAME
-----
-btrfs-restore - try to restore files from a damaged btrfs filesystem(unmounted)
-
-SYNOPSIS
---------
-*btrfs restore* [options] <device> <path> | -l <device>
-
-DESCRIPTION
------------
-*btrfs restore* is used to try to salvage files from a damaged filesystem and
-restore them into <path> or just list the tree roots.
-
-Since current `btrfs-check`(8) or `btrfs-rescue`(8) only has very limited usage,
-*btrfs restore* is normally a better choice.
-
-NOTE: It is recommended to read the following btrfs wiki page if your data is
-not salvaged with default option: +
-https://btrfs.wiki.kernel.org/index.php/Restore
-
-OPTIONS
--------
--s::
-get snapshots, btrfs restore skips snapshots in default.
-
--x::
-get extended attributes.
-
--v::
-verbose.
-
--i::
-ignore errors.
-
--o::
-overwrite directories/files in <path>.
-
--t <bytenr>::
-use <bytenr> to read root tree.
-
--f <bytenr>::
-only restore files that are under specified root whose root bytenr is <bytenr>.
-
--u <mirror>::
-use given superblock mirror identified by <mirror>, it can be 0,1,2.
-
--r <rootid>::
-only restore files that are under specified root whose objectid is <rootid>.
-
--d::
-find dir.
-
--l::
-list tree roots.
-
--D|--dry-run::
-dry run (only list files that would be recovered).
-
---path-regex <regex>::
-restore only filenames matching regex, you have to use following syntax (possibly quoted):
-+
-+^/(|home(|/username(|/Desktop(|/.*))))$+
-
--c::
-ignore case (--path-regrex only).
-
-EXIT STATUS
------------
-*btrfs restore* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-rescue`(8),
-`btrfs-check`(8)
diff --git a/Documentation/btrfs-scrub.asciidoc b/Documentation/btrfs-scrub.asciidoc
new file mode 100644
index 00000000..7750868d
--- /dev/null
+++ b/Documentation/btrfs-scrub.asciidoc
@@ -0,0 +1,94 @@
+btrfs-scrub(8)
+==============
+
+NAME
+----
+btrfs-scrub - scrub btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs scrub* <subcommand> <args>
+
+DESCRIPTION
+-----------
+*btrfs scrub* is used to scrub a btrfs filesystem, which will read all data
+from all disks and verify checksums.
+
+SUBCOMMAND
+----------
+*cancel* <path>|<device>::
+If a scrub is running on the filesystem identified by <path>, cancel it.
++
+Progress is saved in the scrub progress file and scrubbing can be resumed later
+using the scrub resume command.
+If a <device> is given, the corresponding filesystem is found and
+scrub cancel behaves as if it was called on that filesystem.
+
+*resume* [-BdqrR] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device>::
+Resume a canceled or interrupted scrub cycle on the filesystem identified by
+<path> or on a given <device>.
++
+Does not start a new scrub if the last scrub finished successfully.
++
+`Options`
++
+see *scrub start*.
+
+*start* [-BdqrRf] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device>::
+Start a scrub on all devices of the filesystem identified by <path> or on
+a single <device>. If a scrub is already running, the new one fails.
++
+Without options, scrub is started as a background process.
+Progress can be obtained with the *scrub status* command. Scrubbing
+involves reading all data from all disks and verifying checksums. Errors are
+corrected along the way if possible.
++
+The default IO priority of scrub is the idle class. The priority can be
+configured similar to the `ionice`(1) syntax using '-c' and '-n' options.
++
+`Options`
++
+-B::::
+Do not background and print scrub statistics when finished.
+-d::::
+Print separate statistics for each device of the filesystem (-B only).
+-q::::
+Quiet. Omit error messages and statistics.
+-r::::
+Read only mode. Do not attempt to correct anything.
+-R::::
+Raw print mode. Print full data instead of summary.
+-c <ioprio_class>::::
+Set IO priority class (see `ionice`(1) manpage).
+-n <ioprio_classdata>::::
+Set IO priority classdata (see `ionice`(1) manpage).
+-f::::
+Force starting new scrub even if a scrub is already running.
+This is useful when scrub stat record file is damaged.
+
+*status* [-d] <path>|<device>::
+Show status of a running scrub for the filesystem identified by <path> or
+for the specified <device>.
++
+If no scrub is running, show statistics of the last finished or canceled scrub
+for that filesystem or device.
++
+`Options`
++
+-d::::
+Print separate statistics for each device of the filesystem.
+
+EXIT STATUS
+-----------
+*btrfs scrub* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
diff --git a/Documentation/btrfs-scrub.txt b/Documentation/btrfs-scrub.txt
deleted file mode 100644
index 7750868d..00000000
--- a/Documentation/btrfs-scrub.txt
+++ /dev/null
@@ -1,94 +0,0 @@
-btrfs-scrub(8)
-==============
-
-NAME
-----
-btrfs-scrub - scrub btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs scrub* <subcommand> <args>
-
-DESCRIPTION
------------
-*btrfs scrub* is used to scrub a btrfs filesystem, which will read all data
-from all disks and verify checksums.
-
-SUBCOMMAND
-----------
-*cancel* <path>|<device>::
-If a scrub is running on the filesystem identified by <path>, cancel it.
-+
-Progress is saved in the scrub progress file and scrubbing can be resumed later
-using the scrub resume command.
-If a <device> is given, the corresponding filesystem is found and
-scrub cancel behaves as if it was called on that filesystem.
-
-*resume* [-BdqrR] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device>::
-Resume a canceled or interrupted scrub cycle on the filesystem identified by
-<path> or on a given <device>.
-+
-Does not start a new scrub if the last scrub finished successfully.
-+
-`Options`
-+
-see *scrub start*.
-
-*start* [-BdqrRf] [-c <ioprio_class> -n <ioprio_classdata>] <path>|<device>::
-Start a scrub on all devices of the filesystem identified by <path> or on
-a single <device>. If a scrub is already running, the new one fails.
-+
-Without options, scrub is started as a background process.
-Progress can be obtained with the *scrub status* command. Scrubbing
-involves reading all data from all disks and verifying checksums. Errors are
-corrected along the way if possible.
-+
-The default IO priority of scrub is the idle class. The priority can be
-configured similar to the `ionice`(1) syntax using '-c' and '-n' options.
-+
-`Options`
-+
--B::::
-Do not background and print scrub statistics when finished.
--d::::
-Print separate statistics for each device of the filesystem (-B only).
--q::::
-Quiet. Omit error messages and statistics.
--r::::
-Read only mode. Do not attempt to correct anything.
--R::::
-Raw print mode. Print full data instead of summary.
--c <ioprio_class>::::
-Set IO priority class (see `ionice`(1) manpage).
--n <ioprio_classdata>::::
-Set IO priority classdata (see `ionice`(1) manpage).
--f::::
-Force starting new scrub even if a scrub is already running.
-This is useful when scrub stat record file is damaged.
-
-*status* [-d] <path>|<device>::
-Show status of a running scrub for the filesystem identified by <path> or
-for the specified <device>.
-+
-If no scrub is running, show statistics of the last finished or canceled scrub
-for that filesystem or device.
-+
-`Options`
-+
--d::::
-Print separate statistics for each device of the filesystem.
-
-EXIT STATUS
------------
-*btrfs scrub* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
diff --git a/Documentation/btrfs-send.asciidoc b/Documentation/btrfs-send.asciidoc
new file mode 100644
index 00000000..6721428d
--- /dev/null
+++ b/Documentation/btrfs-send.asciidoc
@@ -0,0 +1,58 @@
+btrfs-send(8)
+=============
+
+NAME
+----
+btrfs-send - send data of subvolume(s) to stdout/file.
+
+SYNOPSIS
+--------
+*btrfs send* [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]
+
+DESCRIPTION
+-----------
+Sends the subvolume(s) specified by <subvol> to stdout.
+
+By default, this will send the whole subvolume. To do an incremental
+send, use '-p <parent>'.
+
+If you want to allow btrfs to clone from any additional local snapshots,
+use '-c <clone-src>' (multiple times where applicable). 
+
+You must not specify clone sources unless you guarantee that these snapshots
+are exactly in the same state on both sides, the sender and the receiver.
+
+It is allowed to omit the '-p <parent>' option when '-c <clone-src>' options
+are given, in which case *btrfs send* will determine a suitable parent among the
+clone sources itself.
+
+`Options`
+
+-v::
+Enable verbose debug output. Each occurrence of this option increases the
+verbose level more.
+-e::
+If sending multiple subvols at once, use the new format and omit the <end cmd> between the subvols.
+-p <parent>::
+Send an incremental stream from <parent> to <subvol>.
+-c <clone-src>::
+Use this snapshot as a clone source for an incremental send (multiple allowed).
+-f <outfile>::
+Output is normally written to stdout. To write to a file, use this option.
+An alternative would be to use pipes.
+
+EXIT STATUS
+-----------
+*btrfs send* returns a zero exit status if it succeeds. Non zero is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-receive`(8)
diff --git a/Documentation/btrfs-send.txt b/Documentation/btrfs-send.txt
deleted file mode 100644
index 6721428d..00000000
--- a/Documentation/btrfs-send.txt
+++ /dev/null
@@ -1,58 +0,0 @@
-btrfs-send(8)
-=============
-
-NAME
-----
-btrfs-send - send data of subvolume(s) to stdout/file.
-
-SYNOPSIS
---------
-*btrfs send* [-ve] [-p <parent>] [-c <clone-src>] [-f <outfile>] <subvol> [<subvol>...]
-
-DESCRIPTION
------------
-Sends the subvolume(s) specified by <subvol> to stdout.
-
-By default, this will send the whole subvolume. To do an incremental
-send, use '-p <parent>'.
-
-If you want to allow btrfs to clone from any additional local snapshots,
-use '-c <clone-src>' (multiple times where applicable). 
-
-You must not specify clone sources unless you guarantee that these snapshots
-are exactly in the same state on both sides, the sender and the receiver.
-
-It is allowed to omit the '-p <parent>' option when '-c <clone-src>' options
-are given, in which case *btrfs send* will determine a suitable parent among the
-clone sources itself.
-
-`Options`
-
--v::
-Enable verbose debug output. Each occurrence of this option increases the
-verbose level more.
--e::
-If sending multiple subvols at once, use the new format and omit the <end cmd> between the subvols.
--p <parent>::
-Send an incremental stream from <parent> to <subvol>.
--c <clone-src>::
-Use this snapshot as a clone source for an incremental send (multiple allowed).
--f <outfile>::
-Output is normally written to stdout. To write to a file, use this option.
-An alternative would be to use pipes.
-
-EXIT STATUS
------------
-*btrfs send* returns a zero exit status if it succeeds. Non zero is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-receive`(8)
diff --git a/Documentation/btrfs-show-super.asciidoc b/Documentation/btrfs-show-super.asciidoc
new file mode 100644
index 00000000..1646be3b
--- /dev/null
+++ b/Documentation/btrfs-show-super.asciidoc
@@ -0,0 +1,50 @@
+btrfs-show-super(8)
+====================
+
+NAME
+----
+btrfs-show-super - show btrfs superblock information stored in devices
+
+SYNOPSIS
+--------
+*btrfs-show-super* [options] <dev> [<dev>...]
+
+DESCRIPTION
+-----------
+*btrfs-show-super* is used to print the information of superblock,
+you can specify which mirror to print out.
+
+By default, every device's first superblock will be printed out.
+
+Mainly used for debug purpose.
+
+OPTIONS
+-------
+-f::
+Print full superblock information.
++
+Including the system chunk array and backup roots.
+
+-a::
+Print information of all superblocks.
++
+If this option is given, '-i' option will be ignored.
+
+-i <super_mirror>::
+Specify which mirror to print out.
++
+<super_mirror> is between 0 and 2.
+If several '-i <super_mirror>' are given, only the last one is valid.
+
+-F::
+Attempt to print the superblock even if no superblock magic is found.  May end
+badly.
+
+EXIT STATUS
+-----------
+*btrfs-show-super* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-show-super.txt b/Documentation/btrfs-show-super.txt
deleted file mode 100644
index 1646be3b..00000000
--- a/Documentation/btrfs-show-super.txt
+++ /dev/null
@@ -1,50 +0,0 @@
-btrfs-show-super(8)
-====================
-
-NAME
-----
-btrfs-show-super - show btrfs superblock information stored in devices
-
-SYNOPSIS
---------
-*btrfs-show-super* [options] <dev> [<dev>...]
-
-DESCRIPTION
------------
-*btrfs-show-super* is used to print the information of superblock,
-you can specify which mirror to print out.
-
-By default, every device's first superblock will be printed out.
-
-Mainly used for debug purpose.
-
-OPTIONS
--------
--f::
-Print full superblock information.
-+
-Including the system chunk array and backup roots.
-
--a::
-Print information of all superblocks.
-+
-If this option is given, '-i' option will be ignored.
-
--i <super_mirror>::
-Specify which mirror to print out.
-+
-<super_mirror> is between 0 and 2.
-If several '-i <super_mirror>' are given, only the last one is valid.
-
--F::
-Attempt to print the superblock even if no superblock magic is found.  May end
-badly.
-
-EXIT STATUS
------------
-*btrfs-show-super* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-subvolume.asciidoc b/Documentation/btrfs-subvolume.asciidoc
new file mode 100644
index 00000000..3dd5289b
--- /dev/null
+++ b/Documentation/btrfs-subvolume.asciidoc
@@ -0,0 +1,183 @@
+btrfs-subvolume(8)
+==================
+
+NAME
+----
+btrfs-subvolume - control btrfs subvolume(s)
+
+SYNOPSIS
+--------
+*btrfs subvolume* <subcommand> [<args>]
+
+DESCRIPTION
+-----------
+*btrfs subvolume* is used to control the filesystem to create/delete/list/show
+subvolumes and snapshots.
+
+SUBVOLUME AND SNAPSHOT
+----------------------
+A subvolume in btrfs is not like an LVM logical volume, which is quite
+independent from each other, a btrfs subvolume has its hierarchy and relations
+between other subvolumes.
+
+A subvolume in btrfs can be accessed in two ways.
+
+1. From the parent subvolume +
+When accessing from the parent subvolume, the subvolume can be used just
+like a directory. It can have child subvolumes and its own files/directories.
+
+2. Separate mounted filesystem +
+When `mount`(8) using 'subvol' or 'subvolid' mount option, one can access
+files/directories/subvolumes inside it, but nothing in parent subvolumes.
+
+Also every btrfs filesystem has a default subvolume as its initially top-level
+subvolume, whose subvolume id is 5. (0 is also acceptable as an alias.)
+
+A btrfs snapshot is much like a subvolume, but shares its data(and metadata)
+with other subvolume/snapshot. Due to the capabilities of COW, modifications
+inside a snapshot will only show in a snapshot but not in its source subvolume.
+
+Although in btrfs, subvolumes/snapshots are treated as directories, only
+subvolume/snapshot can be the source of a snapshot, snapshot can not be made
+from normal directories.
+
+SUBCOMMAND
+-----------
+*create* [-i <qgroupid>] [<dest>]<name>::
+Create a subvolume <name> in <dest>.
++
+If <dest> is not given, subvolume <name> will be created in the currently
+directory.
++
+`Options`
++
+-i <qgroupid>::::
+Add the newly created subvolume to a qgroup. This option can be given multiple
+times.
+
+*delete* [options] <subvolume> [<subvolume>...]::
+Delete the subvolume(s) from the filesystem.
++
+If <subvolume> is not a subvolume, btrfs returns an error but continues if
+there are more arguments to process.
++
+The corresponding directory is removed instantly but the data blocks are
+removed later.  The deletion does not involve full commit by default due to
+performance reasons (as a consequence, the subvolume may appear again after a
+crash).  Use one of the '--commit' options to wait until the operation is safely
+stored on the media.
++
+`Options`
++
+-c|--commit-after::::
+wait for transaction commit at the end of the operation
++
+-C|--commit-each::::
+wait for transaction commit after delet each subvolume
+
+*find-new* <subvolume> <last_gen>::
+List the recently modified files in a subvolume, after <last_gen> ID.
+
+*get-default* <path>::
+Get the default subvolume of the filesystem <path>.
++
+The output format is similar to *subvolume list* command.
+
+*list* [options] [-G [\+|-]<value>] [-C [+|-]<value>] [--sort=rootid,gen,ogen,path] <path>::
+List the subvolumes present in the filesystem <path>.
++
+For every subvolume the following information is shown by default. +
+ID <ID> top level <ID> path <path> +
+where path is the relative path of the subvolume to the top level subvolume.
+The subvolume's ID may be used by the subvolume set-default command,
+or at mount time via the subvolid= option.
+If `-p` is given, then parent <ID> is added to the output between ID
+and top level. The parent's ID may be used at mount time via the
+`subvolrootid=` option.
++
+`Options`
++
+-p::::
+print parent ID.
+-a::::
+print all the subvolumes in the filesystem and distinguish between
+absolute and relative path with respect to the given <path>.
+-c::::
+print the ogeneration of the subvolume, aliases: ogen or origin generation.
+-g::::
+print the generation of the subvolume.
+-o::::
+print only subvolumes below specified <path>.
+-u::::
+print the UUID of the subvolume.
+-q::::
+print the parent uuid of subvolumes (and snapshots).
+-R::::
+print the UUID of the sent subvolume, where the subvolume is the result of a receive operation
+-t::::
+print the result as a table.
+-s::::
+only snapshot subvolumes in the filesystem will be listed.
+-r::::
+only readonly subvolumes in the filesystem will be listed.
+-G [+|-]<value>::::
+list subvolumes in the filesystem that its generation is
+>=, \<= or = value. \'\+' means >= value, \'-' means \<= value, If there is
+neither \'+' nor \'-', it means = value.
+-C [+|-]<value>::::
+list subvolumes in the filesystem that its ogeneration is
+>=, \<= or = value. The usage is the same to '-g' option.
+--sort=rootid,gen,ogen,path::::
+list subvolumes in order by specified items.
+you can add \'\+' or \'-' in front of each items, \'+' means ascending,
+\'-' means descending. The default is ascending.
++
+for --sort you can combine some items together by \',', just like
+-sort=+ogen,-gen,path,rootid.
+
+*set-default* <id> <path>::
+Set the subvolume of the filesystem <path> which is mounted as
+default.
++
+The subvolume is identified by <id>, which is returned by the *subvolume list*
+command.
+
+*show* <path>::
+Show information of a given subvolume in the <path>.
+
+*snapshot* [-r] <source> <dest>|[<dest>/]<name>::
+Create a writable/readonly snapshot of the subvolume <source> with the
+name <name> in the <dest> directory.
++
+If only <dest> is given, the subvolume will be named the basename of <source>.
+If <source> is not a subvolume, btrfs returns an error.
+If '-r' is given, the snapshot will be readonly.
+
+*sync* <path> [subvolid...]::
+Wait until given subvolume(s) are completely removed from the filesystem
+after deletion. If no subvolume id is given, wait until all ongoing deletion
+requests are complete. This may take long if new deleted subvolumes appear
+during the sleep interval.
++
+`Options`
++
+-s <N>::::
+sleep N seconds between checks (default: 1)
+
+EXIT STATUS
+-----------
+*btrfs subvolume* returns a zero exit status if it succeeds. A non-zero value is
+returned in case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8),
+`btrfs-subvolume`(8),
+`btrfs-quota`(8),
+`btrfs-qgroup`(8),
diff --git a/Documentation/btrfs-subvolume.txt b/Documentation/btrfs-subvolume.txt
deleted file mode 100644
index 3dd5289b..00000000
--- a/Documentation/btrfs-subvolume.txt
+++ /dev/null
@@ -1,183 +0,0 @@
-btrfs-subvolume(8)
-==================
-
-NAME
-----
-btrfs-subvolume - control btrfs subvolume(s)
-
-SYNOPSIS
---------
-*btrfs subvolume* <subcommand> [<args>]
-
-DESCRIPTION
------------
-*btrfs subvolume* is used to control the filesystem to create/delete/list/show
-subvolumes and snapshots.
-
-SUBVOLUME AND SNAPSHOT
-----------------------
-A subvolume in btrfs is not like an LVM logical volume, which is quite
-independent from each other, a btrfs subvolume has its hierarchy and relations
-between other subvolumes.
-
-A subvolume in btrfs can be accessed in two ways.
-
-1. From the parent subvolume +
-When accessing from the parent subvolume, the subvolume can be used just
-like a directory. It can have child subvolumes and its own files/directories.
-
-2. Separate mounted filesystem +
-When `mount`(8) using 'subvol' or 'subvolid' mount option, one can access
-files/directories/subvolumes inside it, but nothing in parent subvolumes.
-
-Also every btrfs filesystem has a default subvolume as its initially top-level
-subvolume, whose subvolume id is 5. (0 is also acceptable as an alias.)
-
-A btrfs snapshot is much like a subvolume, but shares its data(and metadata)
-with other subvolume/snapshot. Due to the capabilities of COW, modifications
-inside a snapshot will only show in a snapshot but not in its source subvolume.
-
-Although in btrfs, subvolumes/snapshots are treated as directories, only
-subvolume/snapshot can be the source of a snapshot, snapshot can not be made
-from normal directories.
-
-SUBCOMMAND
------------
-*create* [-i <qgroupid>] [<dest>]<name>::
-Create a subvolume <name> in <dest>.
-+
-If <dest> is not given, subvolume <name> will be created in the currently
-directory.
-+
-`Options`
-+
--i <qgroupid>::::
-Add the newly created subvolume to a qgroup. This option can be given multiple
-times.
-
-*delete* [options] <subvolume> [<subvolume>...]::
-Delete the subvolume(s) from the filesystem.
-+
-If <subvolume> is not a subvolume, btrfs returns an error but continues if
-there are more arguments to process.
-+
-The corresponding directory is removed instantly but the data blocks are
-removed later.  The deletion does not involve full commit by default due to
-performance reasons (as a consequence, the subvolume may appear again after a
-crash).  Use one of the '--commit' options to wait until the operation is safely
-stored on the media.
-+
-`Options`
-+
--c|--commit-after::::
-wait for transaction commit at the end of the operation
-+
--C|--commit-each::::
-wait for transaction commit after delet each subvolume
-
-*find-new* <subvolume> <last_gen>::
-List the recently modified files in a subvolume, after <last_gen> ID.
-
-*get-default* <path>::
-Get the default subvolume of the filesystem <path>.
-+
-The output format is similar to *subvolume list* command.
-
-*list* [options] [-G [\+|-]<value>] [-C [+|-]<value>] [--sort=rootid,gen,ogen,path] <path>::
-List the subvolumes present in the filesystem <path>.
-+
-For every subvolume the following information is shown by default. +
-ID <ID> top level <ID> path <path> +
-where path is the relative path of the subvolume to the top level subvolume.
-The subvolume's ID may be used by the subvolume set-default command,
-or at mount time via the subvolid= option.
-If `-p` is given, then parent <ID> is added to the output between ID
-and top level. The parent's ID may be used at mount time via the
-`subvolrootid=` option.
-+
-`Options`
-+
--p::::
-print parent ID.
--a::::
-print all the subvolumes in the filesystem and distinguish between
-absolute and relative path with respect to the given <path>.
--c::::
-print the ogeneration of the subvolume, aliases: ogen or origin generation.
--g::::
-print the generation of the subvolume.
--o::::
-print only subvolumes below specified <path>.
--u::::
-print the UUID of the subvolume.
--q::::
-print the parent uuid of subvolumes (and snapshots).
--R::::
-print the UUID of the sent subvolume, where the subvolume is the result of a receive operation
--t::::
-print the result as a table.
--s::::
-only snapshot subvolumes in the filesystem will be listed.
--r::::
-only readonly subvolumes in the filesystem will be listed.
--G [+|-]<value>::::
-list subvolumes in the filesystem that its generation is
->=, \<= or = value. \'\+' means >= value, \'-' means \<= value, If there is
-neither \'+' nor \'-', it means = value.
--C [+|-]<value>::::
-list subvolumes in the filesystem that its ogeneration is
->=, \<= or = value. The usage is the same to '-g' option.
---sort=rootid,gen,ogen,path::::
-list subvolumes in order by specified items.
-you can add \'\+' or \'-' in front of each items, \'+' means ascending,
-\'-' means descending. The default is ascending.
-+
-for --sort you can combine some items together by \',', just like
--sort=+ogen,-gen,path,rootid.
-
-*set-default* <id> <path>::
-Set the subvolume of the filesystem <path> which is mounted as
-default.
-+
-The subvolume is identified by <id>, which is returned by the *subvolume list*
-command.
-
-*show* <path>::
-Show information of a given subvolume in the <path>.
-
-*snapshot* [-r] <source> <dest>|[<dest>/]<name>::
-Create a writable/readonly snapshot of the subvolume <source> with the
-name <name> in the <dest> directory.
-+
-If only <dest> is given, the subvolume will be named the basename of <source>.
-If <source> is not a subvolume, btrfs returns an error.
-If '-r' is given, the snapshot will be readonly.
-
-*sync* <path> [subvolid...]::
-Wait until given subvolume(s) are completely removed from the filesystem
-after deletion. If no subvolume id is given, wait until all ongoing deletion
-requests are complete. This may take long if new deleted subvolumes appear
-during the sleep interval.
-+
-`Options`
-+
--s <N>::::
-sleep N seconds between checks (default: 1)
-
-EXIT STATUS
------------
-*btrfs subvolume* returns a zero exit status if it succeeds. A non-zero value is
-returned in case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8),
-`btrfs-subvolume`(8),
-`btrfs-quota`(8),
-`btrfs-qgroup`(8),
diff --git a/Documentation/btrfs-zero-log.asciidoc b/Documentation/btrfs-zero-log.asciidoc
new file mode 100644
index 00000000..498ecd67
--- /dev/null
+++ b/Documentation/btrfs-zero-log.asciidoc
@@ -0,0 +1,45 @@
+btrfs-zero-log(8)
+=================
+
+NAME
+----
+btrfs-zero-log - clear out log tree
+
+SYNOPSIS
+--------
+*btrfs-zero-log* <dev>
+
+DESCRIPTION
+-----------
+*btrfs-zero-log* will remove the log tree if log tree is corrupt, which will
+allow you to mount the filesystem again.
+
+The common case where this happens has been fixed a long time ago,
+so it is unlikely that you will see this particular problem.
+
+One can determine whether *btrfs-zero-log* is needed according to the kernel
+backtrace:
+----
+? replay_one_dir_item+0xb5/0xb5 [btrfs]
+? walk_log_tree+0x9c/0x19d [btrfs]
+? btrfs_read_fs_root_no_radix+0x169/0x1a1 [btrfs]
+? btrfs_recover_log_trees+0x195/0x29c [btrfs]
+? replay_one_dir_item+0xb5/0xb5 [btrfs]
+? btree_read_extent_buffer_pages+0x76/0xbc [btrfs]
+? open_ctree+0xff6/0x132c [btrfs]
+----
+
+If the errors are like above, then *btrfs-zero-log* should be used to clear
+the log and the filesystem may be mounted normally again.
+
+NOTE: If you use btrfs as the root filesystem, you may want to include
+*btrfs-zero-log* into initramdisk if the log problems hits you often.
+
+EXIT STATUS
+-----------
+*btrfs-zero-log* will return 0 if no error happened.
+Other exit code means some problems happened.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs-zero-log.txt b/Documentation/btrfs-zero-log.txt
deleted file mode 100644
index 498ecd67..00000000
--- a/Documentation/btrfs-zero-log.txt
+++ /dev/null
@@ -1,45 +0,0 @@
-btrfs-zero-log(8)
-=================
-
-NAME
-----
-btrfs-zero-log - clear out log tree
-
-SYNOPSIS
---------
-*btrfs-zero-log* <dev>
-
-DESCRIPTION
------------
-*btrfs-zero-log* will remove the log tree if log tree is corrupt, which will
-allow you to mount the filesystem again.
-
-The common case where this happens has been fixed a long time ago,
-so it is unlikely that you will see this particular problem.
-
-One can determine whether *btrfs-zero-log* is needed according to the kernel
-backtrace:
-----
-? replay_one_dir_item+0xb5/0xb5 [btrfs]
-? walk_log_tree+0x9c/0x19d [btrfs]
-? btrfs_read_fs_root_no_radix+0x169/0x1a1 [btrfs]
-? btrfs_recover_log_trees+0x195/0x29c [btrfs]
-? replay_one_dir_item+0xb5/0xb5 [btrfs]
-? btree_read_extent_buffer_pages+0x76/0xbc [btrfs]
-? open_ctree+0xff6/0x132c [btrfs]
-----
-
-If the errors are like above, then *btrfs-zero-log* should be used to clear
-the log and the filesystem may be mounted normally again.
-
-NOTE: If you use btrfs as the root filesystem, you may want to include
-*btrfs-zero-log* into initramdisk if the log problems hits you often.
-
-EXIT STATUS
------------
-*btrfs-zero-log* will return 0 if no error happened.
-Other exit code means some problems happened.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/btrfs.asciidoc b/Documentation/btrfs.asciidoc
new file mode 100644
index 00000000..1b3aa293
--- /dev/null
+++ b/Documentation/btrfs.asciidoc
@@ -0,0 +1,121 @@
+btrfs(8)
+========
+
+NAME
+----
+btrfs - control a btrfs filesystem
+
+SYNOPSIS
+--------
+*btrfs* <command> [<args>]
+
+DESCRIPTION
+-----------
+*btrfs* is used to control the filesystem and the files and directories stored.
+It is the tool to create or destroy a snapshot or a subvolume for the
+filesystem, to defrag a file or a directory, flush the data to the disk,
+to resize the filesystem, to scan the device.
+
+It is possible to abbreviate the commands unless the commands are ambiguous.
+For example: it is possible to run *btrfs sub snaps* instead of
+*btrfs subvolume snapshot*.
+But *btrfs file s* is not allowed, because *file s* may be interpreted
+both as *filesystem show* and as *filesystem sync*.
+
+If a command is terminated by '--help', the detailed help is showed.
+If the passed command matches more commands,
+detailed help of all the matched commands is showed. For example
+*btrfs dev --help* shows the help of all *device** commands.
+
+COMMANDS
+--------
+*balance*::
+	Balance btrfs filesystem chunks across single or several devices. +
+	See `btrfs-balance`(8) for details.
+
+*check*::
+	Do off-line check on a btrfs filesystem. +
+	See `btrfs-check`(8) for details.
+
+*device*::
+	Manage devices managed by btrfs, including add/delete/scan and so
+	on. +
+	See `btrfs-device`(8) for details.
+
+*filesystem*::
+	Manage a btrfs filesystem, including label setting/sync and so on. +
+	See `btrfs-filesystem`(8) for details.
+
+*inspect-internal*::
+	Debug tools for developers/hackers. +
+	See `btrfs-inspect-internal`(8) for details.
+
+*property*::
+	Get/set a property from/to a btrfs object. +
+	See `btrfs-property`(8) for details.
+
+*qgroup*::
+	Manage quota group(qgroup) for btrfs filesystem. +
+	See `btrfs-qgroup`(8) for details.
+
+*quota*::
+	Manage quota on btrfs filesystem like enabling/rescan and etc. +
+	See `btrfs-quota`(8) and `btrfs-qgroup`(8) for details.
+
+*receive*::
+	Receive subvolume data from stdin/file for restore and etc. +
+	See `btrfs-receive`(8) for details.
+
+*replace*::
+	Replace btrfs devices. +
+	See `btrfs-replace`(8) for details.
+
+*rescue*::
+	Try to rescue damaged btrfs filesystem. +
+	See `btrfs-rescue`(8) for details.
+
+*restore*::
+	Manage a btrfs filesystem, including label setting/sync and so on. +
+	See `btrfs-restore`(8) for details.
+
+*scrub*::
+	Scrub a btrfs filesystem. +
+	See `btrfs-scrub`(8) for details.
+
+*send*::
+	Send subvolume data to stdout/file for backup and etc. +
+	See `btrfs-send`(8) for details.
+
+*subvolume*::
+	Create/delete/list/manage btrfs subvolume. +
+	See `btrfs-subvolume`(8) for details.
+
+EXIT STATUS
+-----------
+*btrfs* returns a zero exit status if it succeeds. Non zero is returned in
+case of failure.
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8), `ionice`(1),
+`btrfs-balance`(8),
+`btrfs-check`(8),
+`btrfs-device`(8),
+`btrfs-filesystem`(8),
+`btrfs-inspect-internal`(8),
+`btrfs-property`(8),
+`btrfs-qgroup`(8),
+`btrfs-quota`(8),
+`btrfs-receive`(8),
+`btrfs-replace`(8),
+`btrfs-rescue`(8),
+`btrfs-restore`(8),
+`btrfs-scrub`(8),
+`btrfs-send`(8),
+`btrfs-subvolume`(8),
diff --git a/Documentation/btrfs.txt b/Documentation/btrfs.txt
deleted file mode 100644
index 1b3aa293..00000000
--- a/Documentation/btrfs.txt
+++ /dev/null
@@ -1,121 +0,0 @@
-btrfs(8)
-========
-
-NAME
-----
-btrfs - control a btrfs filesystem
-
-SYNOPSIS
---------
-*btrfs* <command> [<args>]
-
-DESCRIPTION
------------
-*btrfs* is used to control the filesystem and the files and directories stored.
-It is the tool to create or destroy a snapshot or a subvolume for the
-filesystem, to defrag a file or a directory, flush the data to the disk,
-to resize the filesystem, to scan the device.
-
-It is possible to abbreviate the commands unless the commands are ambiguous.
-For example: it is possible to run *btrfs sub snaps* instead of
-*btrfs subvolume snapshot*.
-But *btrfs file s* is not allowed, because *file s* may be interpreted
-both as *filesystem show* and as *filesystem sync*.
-
-If a command is terminated by '--help', the detailed help is showed.
-If the passed command matches more commands,
-detailed help of all the matched commands is showed. For example
-*btrfs dev --help* shows the help of all *device** commands.
-
-COMMANDS
---------
-*balance*::
-	Balance btrfs filesystem chunks across single or several devices. +
-	See `btrfs-balance`(8) for details.
-
-*check*::
-	Do off-line check on a btrfs filesystem. +
-	See `btrfs-check`(8) for details.
-
-*device*::
-	Manage devices managed by btrfs, including add/delete/scan and so
-	on. +
-	See `btrfs-device`(8) for details.
-
-*filesystem*::
-	Manage a btrfs filesystem, including label setting/sync and so on. +
-	See `btrfs-filesystem`(8) for details.
-
-*inspect-internal*::
-	Debug tools for developers/hackers. +
-	See `btrfs-inspect-internal`(8) for details.
-
-*property*::
-	Get/set a property from/to a btrfs object. +
-	See `btrfs-property`(8) for details.
-
-*qgroup*::
-	Manage quota group(qgroup) for btrfs filesystem. +
-	See `btrfs-qgroup`(8) for details.
-
-*quota*::
-	Manage quota on btrfs filesystem like enabling/rescan and etc. +
-	See `btrfs-quota`(8) and `btrfs-qgroup`(8) for details.
-
-*receive*::
-	Receive subvolume data from stdin/file for restore and etc. +
-	See `btrfs-receive`(8) for details.
-
-*replace*::
-	Replace btrfs devices. +
-	See `btrfs-replace`(8) for details.
-
-*rescue*::
-	Try to rescue damaged btrfs filesystem. +
-	See `btrfs-rescue`(8) for details.
-
-*restore*::
-	Manage a btrfs filesystem, including label setting/sync and so on. +
-	See `btrfs-restore`(8) for details.
-
-*scrub*::
-	Scrub a btrfs filesystem. +
-	See `btrfs-scrub`(8) for details.
-
-*send*::
-	Send subvolume data to stdout/file for backup and etc. +
-	See `btrfs-send`(8) for details.
-
-*subvolume*::
-	Create/delete/list/manage btrfs subvolume. +
-	See `btrfs-subvolume`(8) for details.
-
-EXIT STATUS
------------
-*btrfs* returns a zero exit status if it succeeds. Non zero is returned in
-case of failure.
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8), `ionice`(1),
-`btrfs-balance`(8),
-`btrfs-check`(8),
-`btrfs-device`(8),
-`btrfs-filesystem`(8),
-`btrfs-inspect-internal`(8),
-`btrfs-property`(8),
-`btrfs-qgroup`(8),
-`btrfs-quota`(8),
-`btrfs-receive`(8),
-`btrfs-replace`(8),
-`btrfs-rescue`(8),
-`btrfs-restore`(8),
-`btrfs-scrub`(8),
-`btrfs-send`(8),
-`btrfs-subvolume`(8),
diff --git a/Documentation/btrfstune.asciidoc b/Documentation/btrfstune.asciidoc
new file mode 100644
index 00000000..96202211
--- /dev/null
+++ b/Documentation/btrfstune.asciidoc
@@ -0,0 +1,44 @@
+btrfstune(8)
+============
+
+NAME
+----
+btrfstune - tune various btrfs filesystem parameters
+
+SYNOPSIS
+--------
+*btrfstune* [options] <dev> [<dev>...]
+
+DESCRIPTION
+-----------
+*btrfstune* is used to tune various btrfs filesystem parameters,you can
+enable/disable some extended features for btrfs.
+
+OPTIONS
+-------
+-S <value>::
+Updates the seeding value.
+A positive value will enable seeding, zero will disable seeding, negtive is not allowed.
+Enable seeding forces a fs readonly so that you can use it to build other filesystems.
+-r::
+Enable extended inode refs.
+-x::
+Enable skinny metadata extent refs.
+-f::
+Allow dangerous changes, e.g. clear the seeding flag. Make sure that you are
+aware of the dangers.
+
+When mounting the new device, btrfs will check whether the seeding flag is set
+when try to open seeding device.  If the user clears the seeding flag of the
+seeding device, the new device will not be mountable. Even setting the seeding
+flag back will not fix this problem, because the generation will be changed at
+that time. Clear the seeding flag may damage the new filesystem.
+
+EXIT STATUS
+-----------
+*btrfstune* will return 0 if no error happened.
+If any problems happened, 1 will be returned.
+
+SEE ALSO
+--------
+`mkfs.btrfs`(8)
diff --git a/Documentation/btrfstune.txt b/Documentation/btrfstune.txt
deleted file mode 100644
index 96202211..00000000
--- a/Documentation/btrfstune.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-btrfstune(8)
-============
-
-NAME
-----
-btrfstune - tune various btrfs filesystem parameters
-
-SYNOPSIS
---------
-*btrfstune* [options] <dev> [<dev>...]
-
-DESCRIPTION
------------
-*btrfstune* is used to tune various btrfs filesystem parameters,you can
-enable/disable some extended features for btrfs.
-
-OPTIONS
--------
--S <value>::
-Updates the seeding value.
-A positive value will enable seeding, zero will disable seeding, negtive is not allowed.
-Enable seeding forces a fs readonly so that you can use it to build other filesystems.
--r::
-Enable extended inode refs.
--x::
-Enable skinny metadata extent refs.
--f::
-Allow dangerous changes, e.g. clear the seeding flag. Make sure that you are
-aware of the dangers.
-
-When mounting the new device, btrfs will check whether the seeding flag is set
-when try to open seeding device.  If the user clears the seeding flag of the
-seeding device, the new device will not be mountable. Even setting the seeding
-flag back will not fix this problem, because the generation will be changed at
-that time. Clear the seeding flag may damage the new filesystem.
-
-EXIT STATUS
------------
-*btrfstune* will return 0 if no error happened.
-If any problems happened, 1 will be returned.
-
-SEE ALSO
---------
-`mkfs.btrfs`(8)
diff --git a/Documentation/fsck.btrfs.asciidoc b/Documentation/fsck.btrfs.asciidoc
new file mode 100644
index 00000000..0bad075b
--- /dev/null
+++ b/Documentation/fsck.btrfs.asciidoc
@@ -0,0 +1,51 @@
+fsck.btrfs(8)
+=============
+
+NAME
+----
+fsck.btrfs - do nothing, successfully
+
+SYNOPSIS
+--------
+*fsck.btrfs* [-aApy] [<device>...]
+
+DESCRIPTION
+-----------
+*fsck.btrfs* is a type of utility that should exist for any filesystem and is
+called during system setup when the corresponding `/etc/fstab` entries
+contain non-zero value for `fs_passno` , see `fstab`(5) for more.
+
+Traditional filesystems need to run their respective fsck utility in case the
+filesystem was not unmounted cleanly and the log needs to be replayed before
+mount. This is not needed for BTRFS. You should set fs_passno to 0.
+
+If you wish to check the consistency of a BTRFS filesystem or repair a damaged
+filesystem, see `btrfs-check`(8). By default the filesystem
+consistency is checked, the repair mode is enabled via '--repair' option (use
+with care!).
+
+OPTIONS
+-------
+The options are all the same and detect if *fsck.btrfs* is executed in
+non-interactive mode and exits with success,
+otherwise prints a message about btrfs check.
+
+EXIT STATUS
+-----------
+There are two possible exit code returned:
+
+0::
+No error
+
+8::
+Operational error, eg. device does not exist
+
+FILES
+-----
+`/etc/fstab`
+
+SEE ALSO
+--------
+`btrfs`(8),
+`fsck`(8),
+`fstab`(5),
diff --git a/Documentation/fsck.btrfs.txt b/Documentation/fsck.btrfs.txt
deleted file mode 100644
index 0bad075b..00000000
--- a/Documentation/fsck.btrfs.txt
+++ /dev/null
@@ -1,51 +0,0 @@
-fsck.btrfs(8)
-=============
-
-NAME
-----
-fsck.btrfs - do nothing, successfully
-
-SYNOPSIS
---------
-*fsck.btrfs* [-aApy] [<device>...]
-
-DESCRIPTION
------------
-*fsck.btrfs* is a type of utility that should exist for any filesystem and is
-called during system setup when the corresponding `/etc/fstab` entries
-contain non-zero value for `fs_passno` , see `fstab`(5) for more.
-
-Traditional filesystems need to run their respective fsck utility in case the
-filesystem was not unmounted cleanly and the log needs to be replayed before
-mount. This is not needed for BTRFS. You should set fs_passno to 0.
-
-If you wish to check the consistency of a BTRFS filesystem or repair a damaged
-filesystem, see `btrfs-check`(8). By default the filesystem
-consistency is checked, the repair mode is enabled via '--repair' option (use
-with care!).
-
-OPTIONS
--------
-The options are all the same and detect if *fsck.btrfs* is executed in
-non-interactive mode and exits with success,
-otherwise prints a message about btrfs check.
-
-EXIT STATUS
------------
-There are two possible exit code returned:
-
-0::
-No error
-
-8::
-Operational error, eg. device does not exist
-
-FILES
------
-`/etc/fstab`
-
-SEE ALSO
---------
-`btrfs`(8),
-`fsck`(8),
-`fstab`(5),
diff --git a/Documentation/mkfs.btrfs.asciidoc b/Documentation/mkfs.btrfs.asciidoc
new file mode 100644
index 00000000..985237f5
--- /dev/null
+++ b/Documentation/mkfs.btrfs.asciidoc
@@ -0,0 +1,140 @@
+mkfs.btrfs(8)
+=============
+
+NAME
+----
+mkfs.btrfs - create a btrfs filesystem
+
+SYNOPSIS
+--------
+*mkfs.btrfs*
+$$[-A|--alloc-start <alloc-start>]$$
+$$[-b|--byte-count <byte-count>]$$
+$$[-d|--data <data-profile>]$$
+$$[-f|--force]$$
+$$[-n|--nodesize <nodesize>]$$
+$$[-l|--leafsize <leafsize>]$$
+$$[-L|--label <label>]$$
+$$[-m|--metadata <metadata profile>]$$
+$$[-M|--mixed]$$
+$$[-s|--sectorsize <sectorsize>]$$
+$$[-r|--rootdir <rootdir>]$$
+$$[-K|--nodiscard]$$
+$$[-O|--features <feature1>[,<feature2>...]]$$
+$$[-U|--uuid <UUID>]$$
+$$[-h]$$
+$$[-V|--version]$$
+$$<device> [<device>...]$$
+
+DESCRIPTION
+-----------
+*mkfs.btrfs*
+is used to create a btrfs filesystem (usually in a disk partition, or an array
+of disk partitions).
+
+<device>
+is the special file corresponding to the device (e.g /dev/sdXX ).
+If multiple devices are specified, btrfs is created
+spanning across the specified  devices.
+
+OPTIONS
+-------
+-A|--alloc-start <offset>::
+Specify the offset from the start of the device at which to start allocations
+in this btrfs filesystem. The default value is zero, or the start of the
+device.  This option is intended only for debugging filesystem resize
+operations.
+
+-b|--byte-count <size>::
+Specify the size of the resultant filesystem. If this option is not used,
+mkfs.btrfs uses all the available storage for the filesystem.
+
+-d|--data <type>::
+Specify how the data must be spanned across the devices specified. Valid
+values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10' or 'single'.
+
+-f|--force::
+Force overwrite when an existing filesystem is detected on the device.
+By default, mkfs.btrfs will not write to the device if it suspects that
+there is a filesystem or partition table on the device already.
+
+-l|--leafsize <size>::
+Alias for --nodesize. Deprecated.
+
+-n|--nodesize <size>::
+Specify the nodesize, the tree block size in which btrfs stores
+data. The default value is 16KB (16384) or the page size, whichever is
+bigger. Must be a multiple of the sectorsize, but not larger than 65536.
+Leafsize always equals nodesize and the options are aliases.
+
+-L|--label <name>::
+Specify a label for the filesystem.
++
+NOTE: <name> should be less than 256 characters.
+
+-m|--metadata <profile>::
+Specify how metadata must be spanned across the devices specified. Valid
+values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10', 'single' or 'dup'.
++
+Single device
+will have dup set by default except in the case of SSDs which will default to
+single. This is because SSDs can remap blocks internally so duplicate blocks
+could end up in the same erase block which negates the benefits of doing
+metadata duplication.
+
+-M|--mixed::
+Mix data and metadata chunks together for more efficient space
+utilization.  This feature incurs a performance penalty in
+larger filesystems.  It is recommended for use with filesystems
+of 1 GiB or smaller.
+
+-s|--sectorsize <size>::
+Specify the sectorsize, the minimum data block allocation unit.
++
+The default
+value is the page size. If the sectorsize differs from the page size, the
+created filesystem may not be mountable by current kernel. Therefore it is not
+recommended to use this option unless you are going to mount it on a system
+with the appropriate page size.
+
+-r|--rootdir <rootdir>::
+Specify a directory to copy into the newly created btrfs filesystem.
++
+NOTE: '-r' option is done completely in userland, and don't need root
+privilege to mount the filesystem.
+
+-K|--nodiscard::
+Do not perform whole device TRIM operation by default.
+
+-O|--features <feature1>[,<feature2>...]::
+A list of filesystem features turned on at mkfs time. Not all features are
+supported by old kernels.
++
+To see all features run:
++
++mkfs.btrfs -O list-all+
+
+-U|--uuid <UUID>::
+Create the filesystem with the specified UUID, which must not already exist on
+the system.
+
+-V|--version::
+Print the *mkfs.btrfs* version and exit.
+
+-h::
+Print help.
+
+UNIT
+----
+As default the unit is the byte, however it is possible to append a suffix
+to the arguments like 'k' for KBytes, 'm' for MBytes...
+
+AVAILABILITY
+------------
+*btrfs* is part of btrfs-progs.
+Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
+further details.
+
+SEE ALSO
+--------
+`btrfs`(8)
diff --git a/Documentation/mkfs.btrfs.txt b/Documentation/mkfs.btrfs.txt
deleted file mode 100644
index 985237f5..00000000
--- a/Documentation/mkfs.btrfs.txt
+++ /dev/null
@@ -1,140 +0,0 @@
-mkfs.btrfs(8)
-=============
-
-NAME
-----
-mkfs.btrfs - create a btrfs filesystem
-
-SYNOPSIS
---------
-*mkfs.btrfs*
-$$[-A|--alloc-start <alloc-start>]$$
-$$[-b|--byte-count <byte-count>]$$
-$$[-d|--data <data-profile>]$$
-$$[-f|--force]$$
-$$[-n|--nodesize <nodesize>]$$
-$$[-l|--leafsize <leafsize>]$$
-$$[-L|--label <label>]$$
-$$[-m|--metadata <metadata profile>]$$
-$$[-M|--mixed]$$
-$$[-s|--sectorsize <sectorsize>]$$
-$$[-r|--rootdir <rootdir>]$$
-$$[-K|--nodiscard]$$
-$$[-O|--features <feature1>[,<feature2>...]]$$
-$$[-U|--uuid <UUID>]$$
-$$[-h]$$
-$$[-V|--version]$$
-$$<device> [<device>...]$$
-
-DESCRIPTION
------------
-*mkfs.btrfs*
-is used to create a btrfs filesystem (usually in a disk partition, or an array
-of disk partitions).
-
-<device>
-is the special file corresponding to the device (e.g /dev/sdXX ).
-If multiple devices are specified, btrfs is created
-spanning across the specified  devices.
-
-OPTIONS
--------
--A|--alloc-start <offset>::
-Specify the offset from the start of the device at which to start allocations
-in this btrfs filesystem. The default value is zero, or the start of the
-device.  This option is intended only for debugging filesystem resize
-operations.
-
--b|--byte-count <size>::
-Specify the size of the resultant filesystem. If this option is not used,
-mkfs.btrfs uses all the available storage for the filesystem.
-
--d|--data <type>::
-Specify how the data must be spanned across the devices specified. Valid
-values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10' or 'single'.
-
--f|--force::
-Force overwrite when an existing filesystem is detected on the device.
-By default, mkfs.btrfs will not write to the device if it suspects that
-there is a filesystem or partition table on the device already.
-
--l|--leafsize <size>::
-Alias for --nodesize. Deprecated.
-
--n|--nodesize <size>::
-Specify the nodesize, the tree block size in which btrfs stores
-data. The default value is 16KB (16384) or the page size, whichever is
-bigger. Must be a multiple of the sectorsize, but not larger than 65536.
-Leafsize always equals nodesize and the options are aliases.
-
--L|--label <name>::
-Specify a label for the filesystem.
-+
-NOTE: <name> should be less than 256 characters.
-
--m|--metadata <profile>::
-Specify how metadata must be spanned across the devices specified. Valid
-values are 'raid0', 'raid1', 'raid5', 'raid6', 'raid10', 'single' or 'dup'.
-+
-Single device
-will have dup set by default except in the case of SSDs which will default to
-single. This is because SSDs can remap blocks internally so duplicate blocks
-could end up in the same erase block which negates the benefits of doing
-metadata duplication.
-
--M|--mixed::
-Mix data and metadata chunks together for more efficient space
-utilization.  This feature incurs a performance penalty in
-larger filesystems.  It is recommended for use with filesystems
-of 1 GiB or smaller.
-
--s|--sectorsize <size>::
-Specify the sectorsize, the minimum data block allocation unit.
-+
-The default
-value is the page size. If the sectorsize differs from the page size, the
-created filesystem may not be mountable by current kernel. Therefore it is not
-recommended to use this option unless you are going to mount it on a system
-with the appropriate page size.
-
--r|--rootdir <rootdir>::
-Specify a directory to copy into the newly created btrfs filesystem.
-+
-NOTE: '-r' option is done completely in userland, and don't need root
-privilege to mount the filesystem.
-
--K|--nodiscard::
-Do not perform whole device TRIM operation by default.
-
--O|--features <feature1>[,<feature2>...]::
-A list of filesystem features turned on at mkfs time. Not all features are
-supported by old kernels.
-+
-To see all features run:
-+
-+mkfs.btrfs -O list-all+
-
--U|--uuid <UUID>::
-Create the filesystem with the specified UUID, which must not already exist on
-the system.
-
--V|--version::
-Print the *mkfs.btrfs* version and exit.
-
--h::
-Print help.
-
-UNIT
-----
-As default the unit is the byte, however it is possible to append a suffix
-to the arguments like 'k' for KBytes, 'm' for MBytes...
-
-AVAILABILITY
-------------
-*btrfs* is part of btrfs-progs.
-Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for
-further details.
-
-SEE ALSO
---------
-`btrfs`(8)
-- 
cgit v1.2.3