LKML Archive on
help / color / mirror / Atom feed
From: (Lennart Sorensen)
To: "Theodore Y. Ts'o" <>,
	Andreas Dilger <>,,
Subject: Re: ext4 ignoring rootfs default mount options
Date: Thu, 15 Mar 2018 14:35:27 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Mar 07, 2018 at 05:50:43PM -0500, Theodore Y. Ts'o wrote:
> Yes, this is a shortcoming in tune2fs.  You can set extended mount
> options using debugfs:
>     debugfs -w -R "set_super_value mount_opts foo,bar" /dev/sda1
> ... but there ought to be some way to support some kind of quoting
> mechanism so that tune2fs can understand when a comma is part of an
> extended option value, as opposed to separating extended options.
> Extended options haven't been used much, so it's not been something
> that has gotten a lot of polish.  Backing up for a bit, is there a
> reason why you need so many mount options when mounting the root file
> sytsem?  Specifically, why do you want to turn off dellayed allocation?

Completely don't trust it.  Also don't do much writing so no real benefit.
Having seen machines get killed by the watchdog come back with blank
chunks in log files is not acceptable.  Getting all user space software
fixed to actually sync properly in all the right places takes forever.

Now for my home machine (especially my mythtv box) it is absoletely on
and a great thing to have.

Len Sorensen

      reply	other threads:[~2018-03-15 18:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 19:03 ext4 ignoring rootfs default mount options Lennart Sorensen
2018-03-07  4:06 ` Theodore Y. Ts'o
2018-03-07 15:14   ` Lennart Sorensen
2018-03-07 16:08     ` Theodore Y. Ts'o
2018-03-07 16:15       ` Lennart Sorensen
2018-03-07 19:13       ` Lennart Sorensen
2018-03-07 22:23         ` Tyson Nottingham
2018-03-07 22:50         ` Theodore Y. Ts'o
2018-03-15 18:35           ` Lennart Sorensen [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).