public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] btrfs: subvol without compression
Date: Fri, 20 Jun 2014 12:07:00 +0200	[thread overview]
Message-ID: <20140620120700.73303d6c@marcec> (raw)
In-Reply-To: <53A020A8.2070809@xunil.at>

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

I don't know if you eventually found an answer yourself, but since nobody else
has replied, here's what I found:

Am Tue, 17 Jun 2014 13:04:08 +0200
schrieb "Stefan G. Weichinger" <lists@xunil.at>:

> 
> ... I am quite happy now with the performance of that new server I am
> preparing.
> 
> See thread "Intel(R) C600 SAS Controller" for that story:
> 
> https://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg146119.html
> 
> Right now I get quite good results when doing backups of the 2 existing
> VMs (which have their virtio-disks on LVM-LVs on the host) ... up to
> 200MB/s ... I can show for reference, if someone is interested.
> 
> I think that is around the possible maximum.
> 
> --->
> 
> The issue I want to share with you is related to a btrfs subvol I have here.
> 
> Block device sda builds the btrfs-pool containing the root-fs:
> 
> # btrfs fi show
> Label: ROOT  uuid: 9133c469-df1e-45f5-a09f-d1b9c75c69da
> 	Total devices 1 FS bytes used 29.47GiB
> 	devid    1 size 500.00GiB used 278.04GiB path /dev/sda
> 
> Btrfs v3.12
> 
> These are the subvolumes (I could/should rm some, but it doesn't matter
> for this issue, afaik):
> 
> # btrfs su list /
> ID 257 gen 4282 top level 5 path __active
> ID 258 gen 4874 top level 5 path __active/root
> ID 266 gen 4772 top level 258 path images
> ID 267 gen 838 top level 258 path images/otrs
> ID 289 gen 4285 top level 258 path images/windows
> ID 538 gen 4874 top level 5 path __active/virt-backup
> 
> 
> fstab has:
> 
> # grep btrfs /etc/fstab
> LABEL=ROOT	/		btrfs	defaults,noatime,compress=lzo	0 0
> LABEL=ROOT	/mnt/virt-backup	btrfs	compress=no,noatime,subvolid=538 0 0
> 
> 
> ... so I want to mount subvolid 538 with disabled compression (to speed
> up backups as the files written to it are compressed on the fly via pigz
> already).

So far nothing in particular stands out, that is, it looks like everything is
correct.

> But after booting I get that dir mounted with compress=lzo (which is
> default).
> 
> # mount | grep btrfs
> /dev/sda on / type btrfs (rw,noatime,compress=lzo,space_cache)
> /dev/sda on /mnt/virt-backup type btrfs
> (rw,noatime,compress=lzo,space_cache)
> 
> remounting works, though:
> 
> booze ~ # mount -o remount,compress=no /mnt/virt-backup/
> 
> booze ~ # mount | grep btrfs
> /dev/sda on / type btrfs (rw,noatime,space_cache)
> /dev/sda on /mnt/virt-backup type btrfs (rw,noatime,space_cache)
> 
> BUT it remounts / without compression as well ... !
> 
> Is it a bug? A mistake or misunderstanding?

From my own google search, at least up to 2011 per-subvolume compression
settings were not possible.  Then, after subsequently searching on the btrfs
wiki for a while, I finally found an answer: no.  See this FAQ entry:

https://btrfs.wiki.kernel.org/index.php/FAQ#Can_I_mount_subvolumes_with_different_mount_options.3F

[...]

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-06-20 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 11:04 [gentoo-user] btrfs: subvol without compression Stefan G. Weichinger
2014-06-17 11:07 ` Stefan G. Weichinger
2014-06-20 10:07 ` Marc Joliet [this message]
2014-06-20 12:01   ` Stefan G. Weichinger
2014-07-07 12:46   ` Stefan G. Weichinger

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=20140620120700.73303d6c@marcec \
    --to=marcec@gmx.de \
    --cc=gentoo-user@lists.gentoo.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