All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Wang Shaoyan <stufever@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: can subvolumes be specified as compressed?
Date: Thu, 29 Jul 2010 16:21:15 +0800	[thread overview]
Message-ID: <4C5139FB.8070504@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTi=_gp3hbXjqCnpzHJRAkBhRZqVZ1V5jhg1B0RAV@mail.gmail.com>

On Thu, 29 Jul 2010 15:50:28 +0800, Wang Shaoyan wrote:
> Hi.
> I want a subvolume in root to be compressed, I try to do this:
> # mkfs.btrfs /dev/sda8
> # mount /dev/sda8 /home/usr/btrfs
> # cd /home/usr/btrfs
> # btrfs subvolume create mysubvolume
> # mount -o compress,subvol=mysubvolume /dev/sda8 some_dir_in_root
> but when I create a file in some_dir_in_root, the file isn't
> compressed at all. why? How can I specify some subvolumes to be
> compressed, and the others Not to be compressed in a single btrfs?

The method that you said is right, by this way, I can create a compressed file
on the specified subvolume.

I think your file has been compressed or is hard to be compressed, so
you found it isn't compressed at all. Just like we use a zip tool to compress
a compressed file, we will find the file isn't compressed at all.

Thanks
Miao

>
> --
> Wang Shaoyan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>


  reply	other threads:[~2010-07-29  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-29  7:50 can subvolumes be specified as compressed? Wang Shaoyan
2010-07-29  8:21 ` Miao Xie [this message]
2010-07-29  8:55   ` Wang Shaoyan
2010-07-29 10:04     ` Miao Xie
2010-07-30  1:29     ` Wang Shaoyan
2010-07-30  2:09       ` Chris Ball
2010-07-30  3:21         ` Wang Shaoyan
2010-07-30  3:50           ` Chris Ball

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=4C5139FB.8070504@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stufever@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 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.