From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f54.google.com ([209.85.213.54]:36598 "EHLO mail-vk0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754126AbbHRVJz (ORCPT ); Tue, 18 Aug 2015 17:09:55 -0400 Received: by vkao123 with SMTP id o123so14599752vka.3 for ; Tue, 18 Aug 2015 14:09:54 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <55D31533.4040409@gmail.com> References: <55D1C8D3.5090501@gmail.com> <55D31533.4040409@gmail.com> Date: Tue, 18 Aug 2015 15:09:54 -0600 Message-ID: Subject: Re: So, wipe it out and start over or keep debugging? From: Chris Murphy To: Austin S Hemmelgarn Cc: Timothy Normand Miller , Btrfs BTRFS Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Tue, Aug 18, 2015 at 5:21 AM, Austin S Hemmelgarn 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