From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Date: Wed, 2 Dec 2015 19:20:12 +0100 Subject: [Ocfs2-devel] [PATCH v2 0/4] Add online file check feature In-Reply-To: <1446013561-22121-1-git-send-email-ghe@suse.com> References: <1446013561-22121-1-git-send-email-ghe@suse.com> Message-ID: <20151202182012.GA21249@amd> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Gang He Cc: mfasheh@suse.com, rgoldwyn@suse.de, linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com, akpm@linux-foundation.org, Greg KH On Wed 2015-10-28 14:25:57, 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 " > /sys/fs/ocfs2/devname/filecheck > or > $# echo "FIX " > /sys/fs/ocfs2/devname/filecheck > Are you sure this is reasonable interface? I mean.... sysfs is supposed to be one value per file. And I don't think its suitable for running commands. ...or returning back results. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html