Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Robert White <rwhite@pobox.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Mounting(multiply)? Options(stored)? Options(barriers)?
Date: Thu, 23 Oct 2014 15:27:06 -0700	[thread overview]
Message-ID: <544980BA.8080007@pobox.com> (raw)

I've got several questions about mount features that I've been unable to 
find definitive answers for.

ITEM: So there are some mount options that I'd like to be able to pin 
onto a media like compress=lzo on a thumb drive I expect to get crowded. 
Is there a feature equivalent to the -o option to tune2fs either present 
or planned?

ITEM: Is there a means (or a plan for a means) to use a subvol as a 
means to prevent/change active features from propigating to a 
subdirectory? An example would be a means to turn off autodefrag or 
compression for a subvolume full of virtual machine images, whilest 
having it active for the bulk of the filesystem.

ITEM: If I make one file system and have subvols /__System /home and 
/VMs and mount those as / /home and /usr/local/VMs respectively, with 
differing feature options for each, will those options be separately 
honored or will the last-mounted or first-mounted subvolume's options 
take dominant effect? Compression, auto-defragment, and commit interval 
being of primary concern.

ITEM: Is there a no-compress attribute (or something similar) for 
negating compress= mount options on specific files or directories? How 
about a no-autodefrag?

(I'm about to set up a system and some standards that may last many 
years and I'm trying to find the reasonable bounds of where I need to do 
hard partitioning.)

--Rob.

             reply	other threads:[~2014-10-23 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 22:27 Robert White [this message]
2014-10-24  2:25 ` Mounting(multiply)? Options(stored)? Options(barriers)? Duncan
2014-10-24  4:07   ` Robert White
2014-10-24  6:46     ` Duncan

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=544980BA.8080007@pobox.com \
    --to=rwhite@pobox.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