From: Goffredo Baroncelli <kreijack@libero.it>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz, Chris Mason <clm@fb.com>,
Goffredo Baroncelli <kreijack@inwind.it>
Subject: [PATCH 5/5] Add new command to man pages: btrfs insp physical-dump
Date: Sun, 24 Jul 2016 13:03:29 +0200 [thread overview]
Message-ID: <1469358209-9427-6-git-send-email-kreijack@libero.it> (raw)
In-Reply-To: <1469358209-9427-1-git-send-email-kreijack@libero.it>
From: Goffredo Baroncelli <kreijack@inwind.it>
Signed-off-by: Goffredo Baroncelli <kreijack@inwind.it>
---
Documentation/btrfs-inspect-internal.asciidoc | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/btrfs-inspect-internal.asciidoc b/Documentation/btrfs-inspect-internal.asciidoc
index 35e2237..0497d08 100644
--- a/Documentation/btrfs-inspect-internal.asciidoc
+++ b/Documentation/btrfs-inspect-internal.asciidoc
@@ -151,6 +151,17 @@ Print raw numbers in bytes.
+
Show the placement of a given file (at offset 'off', default 0) on the disks.
+*physical-dump* [-c <copynr>|-s <stripenr>|-p <paritynr>] <path> [<off>]::
+(needs root privileges)
++
+Dump the disk content of a given file (at offset 'off', default 0).
+For RAID1/RAID10/DUP 'copynr', select which copy will be dumped. For
+RAID5/RAID6, 'paritynr' specifies which parity will be dumped. For
+RAID5/RAID6, 'stripenr' specifies which stripe elemnt will be dumped.
++
+'off' must be a multiple of 4096. 4096 bytes are dumped, even if the file
+is shorter.
+
EXIT STATUS
-----------
*btrfs inspect-internal* returns a zero exit status if it succeeds. Non zero is
--
2.8.1
next prev parent reply other threads:[~2016-07-24 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-24 11:03 [BTRFS-PROGS][PATCH] Add two new commands: 'btrfs insp physical-find' and 'btrfs insp physical-dump' Goffredo Baroncelli
2016-07-24 11:03 ` [PATCH 1/5] Add some helper functions Goffredo Baroncelli
2016-07-24 11:03 ` [PATCH 2/5] New btrfs command: "btrfs inspect physical-find" Goffredo Baroncelli
2016-07-24 11:03 ` [PATCH 3/5] new command btrfs inspect physical-dump Goffredo Baroncelli
2016-07-24 11:03 ` [PATCH 4/5] Add man page for command btrfs insp physical-find Goffredo Baroncelli
2016-07-24 11:03 ` Goffredo Baroncelli [this message]
2016-07-25 2:14 ` [BTRFS-PROGS][PATCH] Add two new commands: 'btrfs insp physical-find' and 'btrfs insp physical-dump' Qu Wenruo
2016-07-25 17:14 ` Goffredo Baroncelli
2016-07-26 1:32 ` Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2016-07-27 17:43 [BTRFS-PROGS][PATCH][V2] " Goffredo Baroncelli
2016-07-27 17:43 ` [PATCH 5/5] Add new command to man pages: btrfs insp physical-dump Goffredo Baroncelli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1469358209-9427-6-git-send-email-kreijack@libero.it \
--to=kreijack@libero.it \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).