All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Bull <sam.hacking@sent.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs send non-root
Date: Sat, 11 Mar 2017 14:54:45 +0000	[thread overview]
Message-ID: <1489244085.6022.8.camel@sent.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

I'm getting an error when trying to send a subvolume. I only seem to be
able to do this as root. The subvolume was created by the user account,
and not root. Could anybody shed some light on why this is failing? Is
there a way to get it working?

$ btrfs send /var/spool/backups/hacking/2017-03-10 > something
ERROR: cannot open '/': Operation not permitted

Also appears I cannot even use btrfs subvolume show:

$ btrfs subvolume show /var/spool/backups/hacking/2017-03-10
ERROR: can't perform the search - Operation not permitted
ERROR: can't find 'var/spool/backups/hacking/2017-03-10'

$ sudo btrfs subvolume show /var/spool/backups/hacking/2017-03-10
/var/spool/backups/hacking/2017-03-10
	Name: 			2017-03-10
	UUID: 			c3a92646-bd6b-7a4f-ae10-
8bd12e569772
	Parent UUID: 		38b66de9-84d3-4848-ae53-
9a2fe861618c
	Received UUID: 		-
	Creation time: 		2017-03-10 19:11:22 +0000
	Subvolume ID: 		564
	Generation: 		753377
	Gen at creation: 	753377
	Parent ID: 		257
	Top level ID: 		257
	Flags: 			readonly
	Snapshot(s):


$ uname -a
Linux sam-laptop 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

$ btrfs --version
btrfs-progs v4.4

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2017-03-11 14:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 14:54 Sam Bull [this message]
2017-03-24 12:14 ` btrfs send non-root David Sterba

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=1489244085.6022.8.camel@sent.com \
    --to=sam.hacking@sent.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.