I ran the following command. It spent a lot of time creating a 1672450048 byte file. Then it stopped writing to the file and started using 100% CPU. It's currently doing no I/O, and it's been doing that for a while now. Is that supposed to happen? On Tue, Aug 18, 2015 at 9:30 AM, Timothy Normand Miller <theosib@xxxxxxxxx> wrote: > In that case, do I need to do all four block devices separately, or > will the tool figure it out? > > On Tue, Aug 18, 2015 at 7:21 AM, Austin S Hemmelgarn > <ahferroin7@xxxxxxxxx> 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. >> >> > > > > -- > Timothy Normand Miller, PhD > Assistant Professor of Computer Science, Binghamton University > http://www.cs.binghamton.edu/~millerti/ > Open Graphics Project -- 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 majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
