I was doing it on an unmounted volume anyhow. On Tue, Aug 18, 2015 at 5:09 PM, Chris Murphy <li...@colorremedies.com> wrote: > On Tue, Aug 18, 2015 at 5:21 AM, Austin S Hemmelgarn > <ahferro...@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
-- Timothy Normand Miller, PhD Assistant Professor of Computer Science, Binghamton University http://www.cs.binghamton.edu/~millerti/ Open Graphics Project -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
