Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Ruben Salzgeber <ruben.salzgeber@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: OS X Time Machine and BTRFS
Date: Tue, 27 Sep 2016 07:16:56 +0500	[thread overview]
Message-ID: <20160927071656.51ef5ef0@natsu> (raw)
In-Reply-To: <CAJCQCtQvaJM-kkP12KRdNpMLAJYcJdi8Fm2b3GgE=Fqm2sUEjg@mail.gmail.com>

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

On Mon, 26 Sep 2016 15:06:39 -0600
Chris Murphy <lists@colorremedies.com> wrote:

> First question is if the directory containing the sparsebundle file
> has xattr +C set on it?

It's not xattr, but chattr. "xattr" manages "extended attributes", i.e.
arbitrary name=value pairs you can set on a file or directory. But +C is just
one of the standard ones.

-- 
With respect,
Roman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-09-27  2:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+Fk0XLfXVaMVTKyovwedBAAAMhpoiuF2b1yuAPbxsOQrkR3=A@mail.gmail.com>
2016-09-26 20:15 ` Fwd: OS X Time Machine and BTRFS Ruben Salzgeber
2016-09-26 20:56   ` Sean Greenslade
2016-09-26 21:45     ` Chris Murphy
     [not found]       ` <CA+Fk0XLGd6ZySLL7RwAeoxK249m+RWAADLJmdncGbaW90L4sPA@mail.gmail.com>
     [not found]         ` <CAJCQCtT=SXBBEEFUxq3Lk_iyL8xHtbe9_v+VqRBVupaQGuVD3Q@mail.gmail.com>
     [not found]           ` <CA+Fk0X+qCjYA9VDdUh=rrxj6xj98cZqcWe83zt+M5XjV1Xrh-Q@mail.gmail.com>
2016-09-27 19:43             ` Chris Murphy
2016-09-26 21:06   ` Chris Murphy
2016-09-27  2:16     ` Roman Mamedov [this message]
2016-09-27  2:27       ` Chris Murphy
2016-09-27 22:57     ` Zygo Blaxell
2016-09-28  1:31       ` Chris Murphy
2016-09-28  2:53         ` Zygo Blaxell

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=20160927071656.51ef5ef0@natsu \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=ruben.salzgeber@gmail.com \
    /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