All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 3/3] e2fsck: allow extent tree optimization to be disabled
Date: Mon, 17 Apr 2017 01:45:05 -0400	[thread overview]
Message-ID: <20170417054505.ggou3yocbnqviqim@thunk.org> (raw)
In-Reply-To: <20170416192430.GB5185@birch.djwong.org>

On Sun, Apr 16, 2017 at 12:24:30PM -0700, Darrick J. Wong wrote:
> 
> /me wonders if there's a way to detect that we're being run by
> initscripts/systemd/whatever on a device that is mounted ro, and skip
> the optimization step to avoid the reboot.

That wasn't actually the reason for this option; but adding feature
where which does this for the root file system mounted read-only, the
optimization is avoided would make sense, yes.

> OTOH I wonder why the initramfs (if available) doesn't just build in
> e2fsck and fsck the root device before mounting the fs...

Debian does this already.  RHEL is just behind the times.  :-)

       	    	 	   	   	- Ted

  reply	other threads:[~2017-04-17  5:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 13:41 [PATCH 1/3] e2fsck: update quota when optimizing the extent tree Theodore Ts'o
2017-04-15 13:41 ` [PATCH 2/3] tests: add new test f_quota_extent_opt Theodore Ts'o
2017-04-15 13:41 ` [PATCH 3/3] e2fsck: allow extent tree optimization to be disabled Theodore Ts'o
2017-04-16 19:24   ` Darrick J. Wong
2017-04-17  5:45     ` Theodore Ts'o [this message]
2017-04-16 19:17 ` [PATCH 1/3] e2fsck: update quota when optimizing the extent tree Darrick J. Wong
2017-04-21  7:37   ` Theodore Ts'o
2017-04-21 16:27     ` Darrick J. Wong
2017-04-21 20:06       ` Theodore Ts'o
2017-04-21 21:15         ` Andreas Dilger
2017-04-22 21:48           ` Theodore Ts'o

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=20170417054505.ggou3yocbnqviqim@thunk.org \
    --to=tytso@mit.edu \
    --cc=darrick.wong@oracle.com \
    --cc=linux-ext4@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 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.