diff options
author | David Sterba <dsterba@suse.cz> | 2014-05-19 17:49:35 +0200 |
---|---|---|
committer | David Sterba <dsterba@suse.cz> | 2014-05-19 17:54:10 +0200 |
commit | a4197dfe24a1964f43734af126188c100885d88e (patch) | |
tree | 2777013a0acac0b7196684afb4faf7725b28886d /Documentation/btrfs-restore.txt | |
parent | aaeae23458aa76a68f5e1b1fb8bf551b04f57f2e (diff) |
btrfs-progs: doc: make all commands and subcommands bold
Italic format is used for parameters and values. also this makes the
text visually separated,
Signed-off-by: David Sterba <dsterba@suse.cz>
Diffstat (limited to 'Documentation/btrfs-restore.txt')
-rw-r--r-- | Documentation/btrfs-restore.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/btrfs-restore.txt b/Documentation/btrfs-restore.txt index c1d1607a..1882f0d0 100644 --- a/Documentation/btrfs-restore.txt +++ b/Documentation/btrfs-restore.txt @@ -7,15 +7,15 @@ btrfs-restore - try to restore files from a damaged btrfs filesystem(unmounted) SYNOPSIS -------- -'btrfs restore' [options] <device> <path> | -l <device> +*btrfs restore* [options] <device> <path> | -l <device> DESCRIPTION ----------- -'btrfs restore' is used to try to salvage files from a damaged filesystem and +*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. +*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: + @@ -58,12 +58,12 @@ list tree roots. EXIT STATUS ----------- -'btrfs restore' returns a zero exist status if it succeeds. Non zero is +*btrfs restore* returns a zero exist status if it succeeds. Non zero is returned in case of failure. AVAILABILITY ------------ -'btrfs' is part of btrfs-progs. Btrfs filesystem is currently under heavy +*btrfs* is part of btrfs-progs. Btrfs filesystem is currently under heavy development, and not suitable for any uses other than benchmarking and review. Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for |