[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5630F932.8050701@oracle.com>
Date: Wed, 28 Oct 2015 09:34:58 -0700
From: Srinivas Eeda <srinivas.eeda@...cle.com>
To: Gang He <ghe@...e.com>, mfasheh@...e.com, rgoldwyn@...e.de
CC: linux-kernel@...r.kernel.org, ocfs2-devel@....oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v2 0/4] Add online file check feature
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists