public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Vlad Dobrotescu <vlad@dobrotescu.ca>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Question: errors=continue behaviour for failed external journal device
Date: Sat, 26 Jul 2014 20:34:45 -0400	[thread overview]
Message-ID: <53D44925.4000903@dobrotescu.ca> (raw)
In-Reply-To: <20140727000733.GV6725@thunk.org>

On 26/07/2014 20:07, Theodore Ts'o wrote:
> On Sat, Jul 26, 2014 at 11:07:59PM +0000, Vlad Dobrotescu wrote:
>> 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?
> So there are two different questions.
>
> If you use errors=continue, there is the chance that the file system
> inconsistencies that discovered could cause further file system
> damage, which might lead to the loss or corruption of data files
> written earlier.  So it's not really recommended for most purposes,
> unless you have some scheme where you are monitoring dmesgs and having
> some strategy to deal with detected file system errors, or when the
> system absolutely, positively must continue running, and this is more
> important than potential data loss.
>
> If the journal block device is not present then the file system can't
> be mounted, and if the system was uncleanly shut down you won't be
> able to recover from the unclean shutdown by replaying the journal.
>
> If the journal block device is *gone*, it is possible to remove the
> external journal block device, and then force a file system repair,
> but if this happens after an unclean shutdown, you may very well lose
> data.
>
> Cheers,
>
> 						- Ted

Sorry if this is a duplicate, but the "Followup" didn't seem to work for me

Thanks for the quick and detailed answer. If I understand it correctly,
the errors= option has nothing to do with journaling, but only with FS
consistency issues (which can be caused by a vanished journal, but also
by other events), while the mounting itself fails in the absence of the
device specified for external journaling, with no fall-back alternative.
Right?

Vlad


  reply	other threads:[~2014-07-27  0:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-26 23:07 Question: errors=continue behaviour for failed external journal device Vlad Dobrotescu
2014-07-27  0:07 ` Theodore Ts'o
2014-07-27  0:34   ` Vlad Dobrotescu [this message]
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=53D44925.4000903@dobrotescu.ca \
    --to=vlad@dobrotescu.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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