public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fast_commit option not recognized/supported by e2fsck?
Date: Mon, 16 May 2022 10:57:30 -0400	[thread overview]
Message-ID: <YoJmWmN6UMnzxLpI@mit.edu> (raw)
In-Reply-To: <CAKuJGC-uO-ywctcRH-i0UUfvzX3Yvep0kpSVi+FQXJjWgYMtdA@mail.gmail.com>

On Mon, May 16, 2022 at 03:00:14PM +0530, Lakshmipathi.G wrote:
> e2fsck 1.46.4 (18-Aug-2021)
> Using EXT2FS Library version 1.46.4, 18-Aug-2021
> $ uname -a
> Linux db 5.13.0-1022-aws #24~20.04.1-Ubuntu SMP Thu Apr 7 22:14:11 UTC
> 2022 aarch64 aarch64 aarch64 GNU/Linux
> 
> Now I did a reboot and the system hangs. It shows the following error
> message. Any thoughts on what's going wrong here? thanks!
> 
> ```
> Begin: Will now check root file system ... fsck from util-linux 2.34
> [/usr/sbin/fsck.ext4 (1) -- /dev/nvme0n1p2] fsck.ext4 -a -C0 /dev/nvme0n1p2
> /dev/nvme0n1p2 has unsupported feature(s): fast_commit
> e2fsck: Get a newer version of e2fsck!

E2fsck 1.46.4 supports fast commit.  I'm guessing what's going on is
that the version of e2fsck in the initial ramdisk is pre-1.46 and so
it didn't support fast commit --- and the root file system is checked
before it is mounted using scripts and binaries in the initrd.


After installing e2fsprogs, you need to update / recreate the
initramfs.  How to do this is distro-dependent, but since you are
using Ubuntu, try this:

   sudo update-initramfs -u -k all

See the man page for update-initramfs and mkinitramfs for more
information.

Cheers,

					- Ted

P.S.  fast commit is a relatively new feature, and we are still fixing
bugs in fast commit.  So please be careful before using it in a
production system, especially if it is mission- or life- critical.  If
you really want to use it, you may want to be using newer kernels than
5.13.0, such as 5.15 LTS.

  reply	other threads:[~2022-05-16 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  9:30 fast_commit option not recognized/supported by e2fsck? Lakshmipathi.G
2022-05-16 14:57 ` Theodore Ts'o [this message]
     [not found]   ` <CAKuJGC__aRPGK2a8e5VK=aDzN92PbJoC3z=AM6x=vJ-g7vd5sA@mail.gmail.com>
2022-05-16 16:20     ` Lakshmipathi.G

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=YoJmWmN6UMnzxLpI@mit.edu \
    --to=tytso@mit.edu \
    --cc=lakshmipathi.g@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox