linux-ext4 - Re: Question: errors=continue behaviour for failed external journal device

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: <20140728150026.GA17378@thunk.org>
Date:	Mon, 28 Jul 2014 11:00:26 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Vlad Dobrotescu <vlad@...rotescu.ca>
Cc:	Lukáš Czerner <lczerner@...hat.com>,
	linux-ext4@...r.kernel.org
Subject: Re: Question: errors=continue behaviour for failed external journal
 device

On Mon, Jul 28, 2014 at 09:31:05AM -0400, Vlad Dobrotescu wrote:
> If you are talking about changes, wouldn't "read-only" be a better fall-back
> alternative for a failed or missing external journal?

For a missing external journal, we simply wouldn't allow the mount to
succeed at all.

The discussion here was about what to do if we detect some kind of
inconsistency in a mounted file system.

Cheers,

					- Ted
--
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