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

[Theodore Ts'o <tytso@mit.edu>]

On Sat, Jul 26, 2014 at 08:34:45PM -0400, Vlad Dobrotescu wrote:
> 
> 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,

The errors= option has to do with how the system will react when it
discovered a file system inconsistency (for example, while deleting a
file, it discovers that the blocks it is trying to free are already
freed, etc.)  errors=continue is the "don't worry, be happy" option
--- and this can sometimes work out, it's much like ignoring a late
mortgage payment notice from the bank.  Most of the time, sooner or
later, it catches up to you.  :-)

> by other events), while the mounting itself fails in the absence of the
> device specified for external journaling, with no fall-back alternative.

Your question about what happens if the journal is missing is much
like the question, "suppose as I have a RAID 0 setup, and I'm missing
one of the disks --- what can we do"?  Basically, nothing.  In a
desperation scenario, there are ways you can forcibly tell the system
to pretend that there is no journal, just like you can pretend that
the system should ignore 20% of a missing RAID 0 array and have the
LVM replace the missing disk with zero blocks --- but results are very
likely to lead to data loss.

Cheers,

					- Ted