All of lore.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send does not work from readonly device
Date: Wed, 24 Sep 2014 13:29:49 +0000 (UTC)	[thread overview]
Message-ID: <pan$afb89$92478dcc$d289358e$905b34a@cox.net> (raw)
In-Reply-To: 16424080.RP99VxSJe8@ubuntu

GEO posted on Tue, 23 Sep 2014 14:58:06 +0200 as excerpted:

> Is that supposed to be that way? Why is readonly not enough to import
> data using btrfs send?

This is a known issue.  The subvolume itself needs to be set read-only, 
and of course that can't be done when the whole filesystem is set read-
only.

But a read-only filesystem should be sufficient, provided it can be 
forced to remain read-only thru the entire send.  I think that's the 
worry, that someone will switch their system from ro to rw in the middle 
of a send, thus screwing it up.

But they're aware of the problem and should eventually have a fix.  But 
I'm not sure how long as there's other work going on too, of course.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  reply	other threads:[~2014-09-24 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 12:58 btrfs send does not work from readonly device GEO
2014-09-24 13:29 ` Duncan [this message]
     [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='pan$afb89$92478dcc$d289358e$905b34a@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.