linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henk Slager <eye1tm@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs-image and btrfs send related queries
Date: Tue, 19 Apr 2016 13:30:25 +0200	[thread overview]
Message-ID: <CAPmG0jbrupUYFdem2yAkFvSLwt9TL1e3pAv-0itGtGMD2AJATQ@mail.gmail.com> (raw)
In-Reply-To: <526644665.2251591.1461058513616.JavaMail.yahoo@mail.yahoo.com>

> I have /dev/sdb , /dev/sdc. Using wipefs -fa I cleared both devices and
> created btrfs on /dev/sdb. Mounted and written some files and unmounted it.
>
> Then I ran btrfs-image /dev/sdc /img1.img and got the dump.

It looks like you imaged the wrong device, that might clarify the IO
errors later on

> Once image created I again ran wipefs -fa /dev/sdb.
>
> Then I ran btrfs-image -r /img1.img /dev/sdc and mounted /dev/sdc.
>
> ls to dumped filesystem shows the file size as original and no file content.
> I guess btrfs-image doesn't modify files stat so i feel it is showing size
> as original.
>
> However running cat on some of files give i/o error
>
> qd67:/btrfs1 # cat shadow.h
> cat: shadow.h: Input/output error
>
> These errors are not on all files on other files, since dump doesn't
> contains any data it just prompts for cat as below.
>
> qd67:/btrfs1 # cat stab.h
> qd67:/btrfs1 # cat stdio_ext.h
>
> Not sure why i/o errors are coming.

  parent reply	other threads:[~2016-04-19 11:30 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
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 [this message]
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=CAPmG0jbrupUYFdem2yAkFvSLwt9TL1e3pAv-0itGtGMD2AJATQ@mail.gmail.com \
    --to=eye1tm@gmail.com \
    --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).