All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dave@jikos.cz>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] Btrfs: make space to keep default mount options
Date: Thu, 20 Sep 2012 13:05:04 +0200	[thread overview]
Message-ID: <20120920110504.GG17430@twin.jikos.cz> (raw)
In-Reply-To: <505982DD.8030408@jp.fujitsu.com>

On Wed, Sep 19, 2012 at 05:31:25PM +0900, Hidetoshi Seto wrote:
> >>  
> >> +	info->mount_opt = info->super_copy->default_mount_opt;
> > 
> > the options have to respect some priority, eg. when I set default
> > options to a filesystem, but mount with a different set, I expect that
> > the explicit flags apply and override the defaults.
> > 
> > I don't remember if this was discussed in the mailinglist or on IRC
> > only, should be easy to dig up if needed.
> 
> At least I don't know whether this was already disscussed or not.

For the subset you've selected, whole-fs default options, I now think we
don't need it, the discussions we had were about option precedence for
per -file, -subvolume, -fs, -mount. At the time of mount only per-mount
and per-fs need to sort their precedence. Any per-file option has to be
evaluated at a specific time eg. when new data are written in case of
compression.

> Now my code gives priority to the default options, and it would not
> be so difficult in case if we have opposing options like "ssd" vs
> "nossd", and "space_cache" vs "no_space_cache"...

Yep, that's what I expect to temporarily disable a specific option, eg.
the space_cache. For that purpose the full set of options with their
no- counterparts would make sense from the usability POV (although there
may be exceptions).

> Or we could use the default options only if there is no options
> specified when it is being mount, but it will make the default
> options useless.

You mean in case of a simple

  mount /dev/ice /mnt

?

This seems like a limited use of the defaults and may be confusing.


david

  reply	other threads:[~2012-09-20 11:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-18  1:25 [PATCH 0/2] Btrfs: set mount options permanently Hidetoshi Seto
2012-09-18  1:28 ` [PATCH 1/2] Btrfs: make space to keep default mount options Hidetoshi Seto
2012-09-18 12:10   ` David Sterba
2012-09-19  8:31     ` Hidetoshi Seto
2012-09-20 11:05       ` David Sterba [this message]
2012-09-18  1:30 ` [PATCH 2/2] Btrfs-progs: add mount-option command Hidetoshi Seto
2012-09-18  2:31   ` Miao Xie
2012-09-18  4:19     ` Roman Mamedov
2012-09-18  8:19       ` Hugo Mills
2012-09-18 12:06         ` David Sterba
2012-09-19  8:32     ` Hidetoshi Seto
2012-09-20 11:14       ` David Sterba
2012-09-18 12:30   ` David Sterba
2012-09-19  8:32     ` Hidetoshi Seto
2012-09-18 10:03 ` R: " Goffredo Baroncelli <kreijack@libero.it>
2012-09-19  8:31   ` Hidetoshi Seto
2012-09-20 11:28   ` David Sterba
2012-09-18 11:37 ` R: " Goffredo Baroncelli <kreijack@libero.it>

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=20120920110504.GG17430@twin.jikos.cz \
    --to=dave@jikos.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.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.