All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brown <davidb@davidb.org>
To: Bernardo Donadio <bcdonadio@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: lsetxattr error when doing send/receive
Date: Tue, 13 May 2014 18:57:46 -0700	[thread overview]
Message-ID: <20140514015746.GA8032@davidb.org> (raw)
In-Reply-To: <lkuapc$si7$1@ger.gmane.org>

On Tue, May 13, 2014 at 08:44:44PM -0300, Bernardo Donadio wrote:
>Hi!
>
>I'm trying to do a send/receive of a snapshot between two disks on 
>Fedora 20 with Linux 3.15-rc5 (and also tried with 3.14 and 3.11) and 
>SELinux disabled, and then I'm receiving the following error:
>
>[root@darwin /]# btrfs subvolume snapshot -r / @.$(date 
>+%Y-%m-%d-%H%M%S)Create a readonly snapshot of '/' in 
>'./@.2014-05-13-203532'
>[root@darwin /]# btrfs send @.2014-05-13-203532 | btrfs receive /mnt/cold/
>At subvol @.2014-05-13-203532
>At subvol @.2014-05-13-203532
>ERROR: lsetxattr bin security.selinux=system_u:object_r:bin_t:s0 
>failed. Operation not supported
>
>I'm missing something? Is this a bug?

Is selinux 'disabled' or just non-enforcing?  If it is enabled, but
even non-enforcing, it still won't allow the security attributes to be
set.

   $ selinuxenabled; echo $?

should give '1' if it is truly disabled.  I believe you have to
disable it at startup time, so if you've changed the config file, you
might need to reboot.

David

  reply	other threads:[~2014-05-14  1:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 23:44 lsetxattr error when doing send/receive Bernardo Donadio
2014-05-14  1:57 ` David Brown [this message]
2014-05-14  3:16   ` Bernardo Donadio
2014-05-14  6:56     ` Chris Murphy
2014-05-14  6:52   ` Chris Murphy
2014-05-14 14:41     ` David Brown
2014-05-15  5:06     ` Bernardo Donadio

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=20140514015746.GA8032@davidb.org \
    --to=davidb@davidb.org \
    --cc=bcdonadio@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 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.