From: Mark Fasheh <mfasheh@suse.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [patch 24/28] ocfs2: add feature document for online file check
Date: Mon, 31 Aug 2015 13:58:32 -0700 [thread overview]
Message-ID: <20150831205832.GC1145@wotan.suse.de> (raw)
In-Reply-To: <55de39c9.NAoA+ITBkmwk4Suv%akpm@linux-foundation.org>
On Wed, Aug 26, 2015 at 03:12:25PM -0700, Andrew Morton wrote:
> From: Gang He <ghe@suse.com>
> Subject: ocfs2: add feature document for online file check
>
> This document describes the OCFS2 online file check feature.
>
> OCFS2 is often used in high-availaibility systems. However, OCFS2 usually
> converts the filesystem to read-only on errors. This may not be
> necessary, since turning the filesystem read-only would affect other
> running processes as well, decreasing availability. Then, a mount option
> (errors=continue) was introduced, which would return the EIO to the
> calling process and terminate furhter processing so that the filesystem is
> not corrupted further. The filesystem is not converted to read-only, and
> the problematic file's inode number is reported in the kernel log. The
> user can try to check/fix this file via online filecheck feature.
>
I know the previous patch was nakked but this is great documentation by the
way and thanks for doing it. Please continue to keep it up to date as your
patch series evolves :)
Thanks again,
--Mark
--
Mark Fasheh
prev parent reply other threads:[~2015-08-31 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 22:12 [Ocfs2-devel] [patch 24/28] ocfs2: add feature document for online file check akpm at linux-foundation.org
2015-08-31 20:58 ` Mark Fasheh [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=20150831205832.GC1145@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
/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