[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-btrfs
Subject:    btrfs send does not work from readonly device
From:       GEO <1g2e3o4 () gmail ! com>
Date:       2014-09-23 12:58:06
Message-ID: 16424080.RP99VxSJe8 () ubuntu
[Download RAW message or body]

Let's say we have a snapshot called "snapshot" on our device "/dev/sdb".
Now we boot a qemu machine and attatch the disk read only (since we do not
want to put our data at risk in the vm, and read only should be enough to
get our snapshot data).

I used

qemu-system-x86_64 -drive -file=/dev/sdb,if=scsi,readonly -hda
<path_to_guest_operating_system>

When we are in the qemu instance (suppose our device  /dev/sdb is mounted
on /mnt/import), we want to import our data now using btrfs send/receive:

btrfs send /mnt/import/snapshot | btrfs receive  /

we get the following problems in syslog due to the fact that our device is
read only:

delayed_refs has NO entry
BTRFS warning (device sdb): btrfs_update_root:151: Aborting unsused
transaction(No space left)
BTRFS warning (device sdb): Skipping commit of aborted transaction.
BTRFS warning (device sdb): cleanup_transaction:1547: Aborting unused
transaction (No space left)

Apart from the snapshot folder being created in / nothing happens, the
process simply hangs forever, with no actual data getting imported.

Is that supposed to be that way? Why is readonly not enough to import data
using btrfs send?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]