linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Henk Slager <eye1tm@gmail.com>
Cc: sri <toyours_sridhar@yahoo.co.in>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-image and btrfs send related queries
Date: Mon, 18 Apr 2016 19:26:19 +0500	[thread overview]
Message-ID: <20160418192619.4749bc17@natsu> (raw)
In-Reply-To: <CAPmG0jbDDG+aLHn+ymBT1Mbd2UZg17rDiwYXu8AYoxb666GXMA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]

On Mon, 18 Apr 2016 16:13:28 +0200
Henk Slager <eye1tm@gmail.com> wrote:

> (your email keeps ending up in gmail spam folder)
> 
> On Mon, Apr 18, 2016 at 9:24 AM, sri <toyours_sridhar@yahoo.co.in> wrote:
> > 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.
> 
> "different disk"  you mention, that is important info. If you doe the
> restore to a image file, that image file is sparse and all data blocks
> are read as zeros.
> 
> However, if you restore to a block device, then you can assume it just
> writes the device blocks for metadata and leaves the rest untouched.
> So trim whole device first or brute-force overwrite completely with
> zeros.
> 
> So maybe the man pages needs some correction / extra notes.
> 
> > I tried on same machine.

Does btrfs-image store/restore the FS UUID? If it does, then potentially both
the source FS and the restored one were visible at the same time to the kernel
with identical UUIDs, and maybe it was actually accessing/mounting the source
one.

-- 
With respect,
Roman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-04-18 14:26 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
2016-04-18 14:13       ` Henk Slager
2016-04-18 14:26         ` Roman Mamedov [this message]
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=20160418192619.4749bc17@natsu \
    --to=rm@romanrm.net \
    --cc=eye1tm@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=toyours_sridhar@yahoo.co.in \
    /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).