From: Andrew Morton <akpm@linux-foundation.org>
To: Gang He <ghe@suse.com>
Cc: mfasheh@suse.com, rgoldwyn@suse.de, linux-kernel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 0/4] ocfs2: add online file check feature
Date: Thu, 9 Jul 2015 14:06:02 -0700 [thread overview]
Message-ID: <20150709140602.eafbc5a3b7660a6c7588e1b6@linux-foundation.org> (raw)
In-Reply-To: <1435123461-3525-1-git-send-email-ghe@suse.com>
On Wed, 24 Jun 2015 13:24:17 +0800 Gang He <ghe@suse.com> 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
This is a userspace feature so it should have user documentation.
Documentation/filesystems/ocfs2.txt is presumably the appropriate
place.
And the availability of the complete user documentation will make the
review of this patchset more productive.
next prev parent reply other threads:[~2015-07-09 21:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 5:24 Gang He
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 [this message]
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=20150709140602.eafbc5a3b7660a6c7588e1b6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--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
all inboxes | Powered by JetHome®