From: Vlad Dobrotescu <vlad@dobrotescu.ca>
To: linux-ext4@vger.kernel.org
Subject: Question: errors=continue behaviour for failed external journal device
Date: Sat, 26 Jul 2014 23:07:59 +0000 (UTC) [thread overview]
Message-ID: <loom.20140727T010632-633@post.gmane.org> (raw)
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?
next reply other threads:[~2014-07-26 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 23:07 Vlad Dobrotescu [this message]
2014-07-27 0:07 ` Question: errors=continue behaviour for failed external journal device Theodore Ts'o
2014-07-27 0:34 ` Vlad Dobrotescu
2014-07-27 1:07 ` Theodore Ts'o
2014-07-28 9:11 ` Lukáš Czerner
2014-07-28 13:17 ` Theodore Ts'o
2014-07-28 13:25 ` Lukáš Czerner
2014-07-28 13:31 ` Vlad Dobrotescu
2014-07-28 15:00 ` Theodore Ts'o
2014-07-28 16:09 ` Darrick J. Wong
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=loom.20140727T010632-633@post.gmane.org \
--to=vlad@dobrotescu.ca \
--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