From: sri <toyours_sridhar@yahoo.co.in>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs-image and btrfs send related queries
Date: Mon, 18 Apr 2016 07:24:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20160418T092105-74@post.gmane.org> (raw)
In-Reply-To: CAPmG0jbp15p6shXq2GtVude_AKTcN2xRDwki0M5m-iiC_Wh51g@mail.gmail.com
I tried btrfs-image and created image file and ran btrfs-image -r to a
different disk. Once recovered and mounted, I can able to see data is
not zeroed out as mentioned in btrfs-image man page.
I tried on same machine.
next prev parent reply other threads:[~2016-04-18 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 12:41 btrfs-image and btrfs send related queries sri
2016-04-15 12:49 ` Hugo Mills
2016-04-15 16:21 ` Henk Slager
2016-04-18 7:24 ` sri [this message]
2016-04-18 14:13 ` Henk Slager
2016-04-18 14:26 ` Roman Mamedov
2016-04-18 19:48 ` Henk Slager
2016-04-19 9:39 ` sri
[not found] ` <526644665.2251591.1461058513616.JavaMail.yahoo@mail.yahoo.com>
2016-04-19 11:30 ` Henk Slager
2016-04-20 11:50 ` sri
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=loom.20160418T092105-74@post.gmane.org \
--to=toyours_sridhar@yahoo.co.in \
--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).