The EXT4 file-system today deprecated its journaled mode of the "data=journal" mount option. Following its deprecation, this mode is planned for removal in the year 2028.

The data=journal mode for EXT4 is where all file data and metadata is written to the file-system's journal before being committed to the main file-system. In the event of a crash or power loss, the journal can then be replayed to recover the data.

The EXT4 data=journal mode is great for those very concerned about data integrity and safety but comes with significant hits to the write performance compared to the default ordered (data=ordered) mode or data=writeback. Using the journaled mode also disables delayed allocation and Direct I/O support.

EXT4 journal deprecated

Per today's Git merge for Linux 7.3, the EXT4 data=journal feature is deprecated and support for it will be removed in early 2028 following the 2027 Linux LTS kernel version.

all 24 comments

sorted by: hot top controversial new old
[–] 2 points 10 hours ago

If you are using data=journal, as I was, the move to ordered requires that you have a battery backup that communicates with the system(s) it backs up.

Apc makes them and the apc kernel module works with them and is very well documented.

Two years to purchase and implement power failover and shutdown is plenty of time.

  • source
  • [–] 8 points 1 day ago (1 child)

    No, the journal is not deprecated. Only data journaling is.

    Metadata is still journaled and is what most people have been using all this time.

  • source
  • hideshow 1 child comment
  • [–] 7 points 1 day ago*

    Okay, but no mention of alternative modes of operation for "those very concerned about data integrity and safety"?

  • source
  • [–] 7 points 1 day ago (4 children)

    What reason is there to use EXT4 if not for the journal?

    Just use F2FS or BTRFS at that point. (or ZFS if you're fine with out-of-tree)

  • source
  • hideshow 4 child comments
  • [–] 4 points 1 day ago (3 children)

    They are not removing the journal.

  • source
  • parent
  • hideshow 3 child comments
  • [+] -8 points 1 day ago (2 children)

    Ahem...

    Per today's Git merge for Linux 7.3, the EXT4 data=journal feature is deprecated and support for it will be removed in early 2028 following the 2027 Linux LTS kernel version.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 day ago* (1 child)

    data=journal is just one mode of journaling. Not the entire feature.

    Journaling all of the data is very expensive and slow and no one was using it.

    Metadata journaling as always the main feature and is still present.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 2 days ago

    That’s too bad. It was great for use as a root fs on VMware when you had an unreliable NFS storage. Kept every VM from needing an FSCK on recovery.

  • source
  • [–] 2 points 1 day ago (4 children)

    But why they need to remove it? Maybe just left it as a non-recommended option or just create an alternative. A great amount of people, like me for example, have a volatile enviroment that makes this a need.

    Although I do prefer Btrfs for that task, I understand why some people need it in Ext4.

  • source
  • hideshow 4 child comments
  • [–] 6 points 1 day ago (2 children)

    But why they need to remove it?

    Most likely maintainers are looking to reduce the maintenance burden produced by a feature that had very low uptake (assuming, as others are saying, that it's only data journalling and not metadata journalling that's being removed).

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 day ago (1 child)

    Yeah, it might be that and that sounds fair, but still they could just make something like an external extension or module or something like that, or outright looking for someone who could make a more modern, maintenable, fast, lightweight and efficient alternative (using, i.e. io_uring).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 11 hours ago*

    I don't think there's anything preventing someone from forking it into an out-of-tree patchset or alternative module, if they're enthusiastic about the feature. But I'm pretty sure that searching for someone to rewrite a non-core function that most people don't care about is way outside what Linus and the various core maintainers want to do with their time. Normally open source is about people scratching their own itches.

  • source
  • parent
  • [–] 3 points 1 day ago

    Although I do prefer Btrfs for that task, I understand why some people need it in Ext4.

    i was going to say something along these lines -- we switched at a previous last shop to something more reliable and it got rid of our problems, but our fleet was probably newer and smaller than yours; around 5k debian 8/9 bare iron servers back around 2017.

  • source
  • parent
  • [–] 3 points 1 day ago (8 children)

    Wasn't the journal the main selling point in the transition from EXT2 to EXT3? This seems kinda backwards, what even is the rational?

  • source
  • hideshow 8 child comments
  • [–] 6 points 1 day ago (7 children)

    The metadata journal is still there. Most people are not journaling their data, it's too slow.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 1 day ago (6 children)

    Ah, I see! From googling "data=ordered" is the default and does what you said. Still, why not leave it for those that want it?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 1 day ago (5 children)

    Maintenance is not free? They still have to test it at the very least.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 1 day ago (4 children)

    Yeah, but I thought the philosophy was not to break userspace. I'm fine with the removal if absolutely nobody uses it, but some have commented here being users of the feature

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 5 hours ago (2 children)

    I think its userspace too. But I don't know how this is defined anyway. Otherwise removing any drivers in the Kernel would count as breaking userspace too, and they do it all the time.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 4 hours ago (1 child)

    The removed drivers are usually those that are really old and not used by anybody (using the latest kernel), so it's a bit different.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 4 hours ago

    Sure, but I think the point is that most people don't even use data=journal option with EXT4. If I understand it right. But I get it, EXT4 is a common and stable and important part of Linux. Removing any feature, even if it not that many uses them, sounds wrong to me too. My previous point was actually trying to define if this falls into breaking userspace, and I just took a random example that affects userspace too. Because Linus doesn't say "we are only allowed to break userspace, if just a few people use it", he does not want do it at all. My point was, a driver in Kernel doesn't fall under userspace.

  • source
  • parent