From: Gang He <ghe@suse.com>
To: mfasheh@suse.com, ghe@suse.com, rgoldwyn@suse.de
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
akpm@linux-foundation.org
Subject: [PATCH 0/4] ocfs2: add online file check feature
Date: Wed, 24 Jun 2015 13:24:17 +0800 [thread overview]
Message-ID: <1435123461-3525-1-git-send-email-ghe@suse.com> (raw)
When there are errors in the ocfs2 filesystem,
they are usually accompanied by the inode number which caused the error.
This inode number would be the input to fixing the file.
One of these options could be considered:
A file in the sys filesytem which would accept inode numbers.
This could be used to communication back what has to be fixed or is fixed.
You could write:
$# echo "CHECK <inode>" > /sys/fs/ocfs2/devname/filecheck
or
$# echo "FIX <inode>" > /sys/fs/ocfs2/devname/filecheck
Gang He (4):
ocfs2: export ocfs2_kset for online file check
ocfs2: sysfile interfaces for online file check
ocfs2: create/remove sysfile for online file check
ocfs2: check/fix inode block for online file check
fs/ocfs2/Makefile | 3 +-
fs/ocfs2/filecheck.c | 569 +++++++++++++++++++++++++++++++++++++++++++++++++
fs/ocfs2/filecheck.h | 48 +++++
fs/ocfs2/inode.c | 196 ++++++++++++++++-
fs/ocfs2/inode.h | 3 +
fs/ocfs2/ocfs2_trace.h | 2 +
fs/ocfs2/stackglue.c | 3 +-
fs/ocfs2/stackglue.h | 2 +
fs/ocfs2/super.c | 5 +
9 files changed, 823 insertions(+), 8 deletions(-)
create mode 100644 fs/ocfs2/filecheck.c
create mode 100644 fs/ocfs2/filecheck.h
--
2.1.2
next reply other threads:[~2015-06-24 5:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 5:24 Gang He [this message]
2015-06-24 5:24 ` [PATCH 1/4] ocfs2: export ocfs2_kset for online file check Gang He
2015-06-24 5:24 ` [PATCH 2/4] ocfs2: sysfile interfaces " Gang He
2015-06-24 5:24 ` [PATCH 3/4] ocfs2: create/remove sysfile " Gang He
2015-06-24 5:24 ` [PATCH 4/4] ocfs2: check/fix inode block " Gang He
2015-07-03 7:28 ` [Ocfs2-devel] [PATCH 0/4] ocfs2: add online file check feature Joseph Qi
2015-07-03 8:04 ` Gang He
2015-07-09 21:06 ` Andrew Morton
2015-07-10 7:26 ` Gang He
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=1435123461-3525-1-git-send-email-ghe@suse.com \
--to=ghe@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=rgoldwyn@suse.de \
/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
all inboxes | Powered by JetHome®