On 2015-08-18 17:09, Chris Murphy wrote:
In theory, it might be useful, but we would need to slap a big obnoxious warning on such functionality. I don't think it's possible right now, and as such we should do something to account for the possibility of someone trying it.On Tue, Aug 18, 2015 at 5: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.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.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
