linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Ali AlipourR <alipoor90@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: subvolume / folder compression flag
Date: Mon, 15 Dec 2014 07:27:53 -0500	[thread overview]
Message-ID: <548ED3C9.5080508@gmail.com> (raw)
In-Reply-To: <CABvhJLiV4iPkin_XU-Ud3a0KiOLNv07m6whqZtNymDQd+1WHGw@mail.gmail.com>

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

On 2014-12-13 21:59, Ali AlipourR wrote:
> Hi,
>
> 1- Do setting compression flag per subvolume is implemented?
> (I did read on wiki that it is not implemented, but I can set it via
> "btrfs  property")
AFAIK, it's the compression related mount options that don't work 
per-subvolume.  Using chattr +c or btrfs properties should work (I don't 
know if btrfs properties are inherited by default though).
>
> 2- If I set compression flag via "btrfs property" or "chattr" on a
> subvolume, and rsync files without compression flag from ext4 file
> system and preserve attributes by rsync -AX, do these files on that
> btrfs subvolume will be compressed?
> I mean do files will be compressed even if their compression flag
> wasn't set, and just their subvolume compression flag was set?
>
> 3- what if I do same as 2 but on normal folder instead of subvolume
> (chattr +c that folder), Do files within that folder will be
> compressed even if their compression flag wasn't set?
These depend on many things.  Using -A won't (barring bugs in rsync) 
affect anything set by either chattr or btrfs properties.  Using -X 
MIGHT clear the btrfs properties, but I don't think it affects stuff set 
by chattr unless you are root (I know that it doesn't preserve 
immutability or append-only flags unless you are root).  In both 2 and 
3, I believe that the files will be uncompressed on the btrfs volume.


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

      parent reply	other threads:[~2014-12-15 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-14  2:59 subvolume / folder compression flag Ali AlipourR
2014-12-14  7:38 ` Robert White
2014-12-15 12:27 ` Austin S Hemmelgarn [this message]

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=548ED3C9.5080508@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=alipoor90@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).