linux-ext4 - Re: 4.7.0-rc7 ext4 error in dx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.12.1607252154570.8973@trent.utfs.org>
Date:	Mon, 25 Jul 2016 21:55:06 -0700 (PDT)
From:	Christian Kujau <lists@...dbynature.de>
To:	Theodore Ts'o <tytso@....edu>
cc:	Johannes Stezenbach <js@...21.net>, linux-ext4@...r.kernel.org
Subject: Re: 4.7.0-rc7 ext4 error in dx_probe

On Mon, 18 Jul 2016, Theodore Ts'o wrote:
> system corruption detected earlier.  The problem is people
> unfortunately run with their file systems set to errors=continue,

The first thing I do after creating an ext4 fs is to set this to 
errors=remount-ro :-)

Isn't "remount-ro" was XFS is doing when it detects an error? Are
there plans to switch the default for ext4 to that? I never understood why 
errors=continue was the default, thanks for explaining that.

Christian.
-- 
BOFH excuse #339:

manager in the cable duct
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html