From: GEO <1g2e3o4@gmail.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: btrfs send does not work from readonly device
Date: Tue, 23 Sep 2014 14:58:06 +0200 [thread overview]
Message-ID: <16424080.RP99VxSJe8@ubuntu> (raw)
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?
next reply other threads:[~2014-09-23 12:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 12:58 GEO [this message]
2014-09-24 13:29 ` btrfs send does not work from readonly device Duncan
[not found] ` <CAOsFrTcVrWjSks0K-NzokHinBZVRxGGwmRzG_tdzxaU7AAC=xQ@mail.gmail.com>
2014-09-25 19:39 ` G EO
[not found] ` <vXff1o01A11vvw101XfhvK>
2014-09-26 1:47 ` Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16424080.RP99VxSJe8@ubuntu \
--to=1g2e3o4@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).