From: Gang He <ghe@suse.com>
To: mfasheh@suse.com, rgoldwyn@suse.de, ghe@suse.com
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
akpm@linux-foundation.org
Subject: [PATCH v4 0/5] Add online file check feature
Date: Mon, 29 Feb 2016 13:17:57 +0800 [thread overview]
Message-ID: <1456723082-13838-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 "<inode>" > /sys/fs/ocfs2/devname/filecheck/check
or
$# echo "<inode>" > /sys/fs/ocfs2/devname/filecheck/fix
Compare with third version, I add buffer_jbd() check in inode block fix/writing
dirty buffer back, make unsigned short type to unsigned int type for members
in ocfs2_filecheck_entry struct, add feature document in this patch set.
Compare with second version, I re-design filecheck sysfs interfaces, there
are three sysfs files(check, fix and set) under filecheck directory(see above),
sysfs will accept only one argument <inode>. Second, I adjust some code in
ocfs2_filecheck_repair_inode_block() function according to upstream feedback,
we cannot just add VALID_FL flag back as a inode block fix, then we will not
fix this field corruption currently until having a complete solution.
Compare with first version, I use strncasecmp instead of double strncmp
functions. Second, update the source file contribution vendor.
Gang He (5):
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
ocfs2: add feature document for online file check
.../filesystems/ocfs2-online-filecheck.txt | 94 ++++
fs/ocfs2/Makefile | 3 +-
fs/ocfs2/filecheck.c | 606 +++++++++++++++++++++
fs/ocfs2/filecheck.h | 49 ++
fs/ocfs2/inode.c | 225 +++++++-
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 +
10 files changed, 981 insertions(+), 11 deletions(-)
create mode 100644 Documentation/filesystems/ocfs2-online-filecheck.txt
create mode 100644 fs/ocfs2/filecheck.c
create mode 100644 fs/ocfs2/filecheck.h
--
2.1.2
next reply other threads:[~2016-02-29 5:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 5:17 Gang He [this message]
2016-02-29 5:17 ` [PATCH v4 1/5] ocfs2: export ocfs2_kset for online file check Gang He
2016-02-29 5:17 ` [PATCH v4 2/5] ocfs2: sysfile interfaces " Gang He
2016-03-09 5:40 ` [Ocfs2-devel] " Eric Ren
2016-03-21 22:57 ` Mark Fasheh
2016-03-21 23:05 ` Andrew Morton
2016-03-21 23:38 ` [Ocfs2-devel] " Mark Fasheh
2016-03-22 1:01 ` Andrew Morton
2016-03-22 2:15 ` Gang He
2016-02-29 5:18 ` [PATCH v4 3/5] ocfs2: create/remove sysfile " Gang He
2016-02-29 5:18 ` [PATCH v4 4/5] ocfs2: check/fix inode block " Gang He
2016-03-09 5:41 ` [Ocfs2-devel] " Eric Ren
2016-03-21 22:16 ` Mark Fasheh
2016-02-29 5:18 ` [PATCH v4 5/5] ocfs2: add feature document " 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=1456723082-13838-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®