linux-ext4 - 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-next>] [day] [month] [year] [list]

Message-ID: <loom.20140727T010632-633@post.gmane.org>
Date:	Sat, 26 Jul 2014 23:07:59 +0000 (UTC)
From:	Vlad Dobrotescu <vlad@...rotescu.ca>
To:	linux-ext4@...r.kernel.org
Subject: Question: errors=continue behaviour for failed external journal device

If this isn't the proper place for this question, please point me in 
the right direction.

I couldn't find any description on Ext4's behaviour when mounted 
with errors=continue and external journal if the journal block device 
is unavailable at mount time (or becomes unavailable at some point).

I would be using CentOS 7 (kernel 3.10.0-123.4.4.el7 x86_64) and 
(probably) full data journaling on a SSD. Can someone help?

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