From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Theodore Ts'o <tytso@mit.edu>, Johannes Stezenbach <js@sig21.net>,
linux-ext4@vger.kernel.org
Subject: Re: 4.7.0-rc7 ext4 error in dx_probe
Date: Thu, 28 Jul 2016 10:00:57 +1000 [thread overview]
Message-ID: <20160728000057.GW16044@dastard> (raw)
In-Reply-To: <alpine.DEB.2.20.12.1607252154570.8973@trent.utfs.org>
On Mon, Jul 25, 2016 at 09:55:06PM -0700, Christian Kujau wrote:
> On Mon, 18 Jul 2016, Theodore Ts'o wrote:
> > system corruption detected earlier. The problem is people
> > unfortunately run with their file systems set to errors=continue,
>
> The first thing I do after creating an ext4 fs is to set this to
> errors=remount-ro :-)
>
> Isn't "remount-ro" was XFS is doing when it detects an error?
No, XFS shuts down and prevents all further access to the filesystem
when it hits a corruption that it can't continue onwards from. This
is not optional in XFS - to continue after such a corruption is
detected will only make the corruption worse....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-07-28 0:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 10:57 4.7.0-rc7 ext4 error in dx_probe Johannes Stezenbach
2016-07-18 13:38 ` Theodore Ts'o
2016-07-18 14:17 ` Johannes Stezenbach
2016-07-27 11:58 ` Johannes Stezenbach
[not found] ` <7849bcd2-142d-0a12-0a04-7d0c3b6d788f@etorok.net>
2016-08-05 10:35 ` Johannes Stezenbach
2016-08-05 17:02 ` Darrick J. Wong
2016-08-05 18:11 ` Johannes Stezenbach
2016-08-05 19:15 ` Darrick J. Wong
2016-08-08 3:56 ` Theodore Ts'o
2016-08-08 6:28 ` Darrick J. Wong
2016-08-08 16:08 ` Theodore Ts'o
2016-08-08 16:55 ` Darrick J. Wong
2016-08-08 21:13 ` Török Edwin
2016-08-09 2:37 ` Darrick J. Wong
2016-08-09 7:12 ` Török Edwin
2016-08-17 14:27 ` Török Edwin
2016-08-17 23:28 ` Darrick J. Wong
2016-08-22 7:33 ` Török Edwin
2016-09-01 16:40 ` Darrick J. Wong
2016-08-17 20:02 ` Johannes Stezenbach
2016-08-18 7:44 ` Török Edwin
2016-07-26 4:55 ` Christian Kujau
2016-07-28 0:00 ` Dave Chinner [this message]
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=20160728000057.GW16044@dastard \
--to=david@fromorbit.com \
--cc=js@sig21.net \
--cc=linux-ext4@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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