From: Chris Murphy <lists@colorremedies.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Timothy Normand Miller <theosib@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: So, wipe it out and start over or keep debugging?
Date: Tue, 18 Aug 2015 15:09:54 -0600 [thread overview]
Message-ID: <CAJCQCtT3kGNZ3vcvhjP==6L402Zys=a3mHexErajTSDDbNBdNw@mail.gmail.com> (raw)
In-Reply-To: <55D31533.4040409@gmail.com>
On Tue, Aug 18, 2015 at 5:21 AM, Austin S Hemmelgarn
<ahferroin7@gmail.com> wrote:
> On 2015-08-17 14:52, Timothy Normand Miller wrote:
>>
>> I'm not sure if I'm doing this wrong. Here's what I'm seeing:
>>
>> # btrfs-image -c9 -t4 -w /mnt/btrfs ~/btrfs_dump.z
>> Superblock bytenr is larger than device size
>> Open ctree failed
>> create failed (No such file or directory)
>
>
> For the source, you need to specify the underlying block device, not the top
> of the mounted filesystem. It's trying to read the directory as a block
> device and getting very confused. We should probably add some kind of check
> to btrfs-image to warn about that.
Should it even be possible to use btrfs-image on a mounted volume? If
it's written to at all, the collected image is going to be
inconsistent.
--
Chris Murphy
next prev parent reply other threads:[~2015-08-18 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-15 21:46 So, wipe it out and start over or keep debugging? Timothy Normand Miller
2015-08-17 11:43 ` Austin S Hemmelgarn
2015-08-17 18:52 ` Timothy Normand Miller
2015-08-18 11:21 ` Austin S Hemmelgarn
2015-08-18 13:30 ` Timothy Normand Miller
2015-08-18 15:10 ` Timothy Normand Miller
2015-08-18 15:56 ` Austin S Hemmelgarn
2015-08-18 21:09 ` Chris Murphy [this message]
2015-08-18 21:10 ` Timothy Normand Miller
2015-08-20 11:35 ` Austin S Hemmelgarn
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='CAJCQCtT3kGNZ3vcvhjP==6L402Zys=a3mHexErajTSDDbNBdNw@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=theosib@gmail.com \
/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).