public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Srinivas Eeda <srinivas.eeda@oracle.com>
To: Gang He <ghe@suse.com>, mfasheh@suse.com, rgoldwyn@suse.de
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v2 0/4] Add online file check feature
Date: Wed, 28 Oct 2015 09:34:58 -0700	[thread overview]
Message-ID: <5630F932.8050701@oracle.com> (raw)
In-Reply-To: <1446013561-22121-1-git-send-email-ghe@suse.com>

Hi Gang,

thank you for implementing this. I would like to understand this better 
on where and how it helps ... would you mind sharing couple 
examples(real scenarios).

Thanks,
--Srini


On 10/27/2015 11:25 PM, Gang He wrote:
> 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
>
> Compare with first version, I use strncasecmp instead of double strncmp
> functions. Second, update the source file contribution vendor.
>
> 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   | 566 +++++++++++++++++++++++++++++++++++++++++++++++++
>   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, 820 insertions(+), 8 deletions(-)
>   create mode 100644 fs/ocfs2/filecheck.c
>   create mode 100644 fs/ocfs2/filecheck.h
>


  parent reply	other threads:[~2015-10-28 16:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28  6:25 [PATCH v2 0/4] Add online file check feature Gang He
2015-10-28  6:25 ` [PATCH v2 1/4] ocfs2: export ocfs2_kset for online file check Gang He
2015-11-24 21:47   ` Mark Fasheh
2015-10-28  6:25 ` [PATCH v2 2/4] ocfs2: sysfile interfaces " Gang He
2015-11-03  7:20   ` Junxiao Bi
2015-11-03  7:54     ` Gang He
2015-11-03  8:20       ` Junxiao Bi
2015-11-03  8:30         ` Gang He
2015-11-24 21:46         ` Mark Fasheh
2015-11-24 21:55           ` [Ocfs2-devel] " Srinivas Eeda
2015-11-25  3:29           ` Gang He
2015-11-25  4:43             ` Junxiao Bi
2015-11-25  5:11               ` Gang He
2015-12-18 22:37             ` Mark Fasheh
2015-11-25  4:33           ` Junxiao Bi
2015-11-24 21:52   ` [Ocfs2-devel] " Mark Fasheh
2015-10-28  6:26 ` [PATCH v2 3/4] ocfs2: create/remove sysfile " Gang He
2015-11-24 21:53   ` Mark Fasheh
2015-10-28  6:26 ` [PATCH v2 4/4] ocfs2: check/fix inode block " Gang He
2015-11-03  7:12   ` Junxiao Bi
2015-11-03  8:15     ` Gang He
2015-11-03  8:29       ` Junxiao Bi
2015-11-03  8:47         ` Gang He
2015-11-03  9:01           ` Junxiao Bi
2015-11-03  9:25             ` Gang He
2015-11-24 22:16     ` [Ocfs2-devel] " Mark Fasheh
2015-11-25  4:11       ` Junxiao Bi
2015-11-25  5:04         ` Gang He
2015-11-25  5:44           ` Junxiao Bi
2015-10-28 16:34 ` Srinivas Eeda [this message]
2015-10-29  4:44   ` [Ocfs2-devel] [PATCH v2 0/4] Add online file check feature Gang He
2015-10-29  7:46     ` Srinivas Eeda
2015-10-29  8:26       ` Gang He
2015-12-02 18:20 ` Pavel Machek
2015-12-03  2:05   ` Gang He
2015-12-03  5:17     ` Greg KH
2015-12-04  8:36       ` Gang He
2015-12-04  9:20         ` Pavel Machek
2015-12-04 16:40         ` Greg KH
2015-12-07  3:33           ` 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=5630F932.8050701@oracle.com \
    --to=srinivas.eeda@oracle.com \
    --cc=ghe@suse.com \
    --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