Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754381AbbGIVGI (ORCPT ); Thu, 9 Jul 2015 17:06:08 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:51556 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754005AbbGIVGD (ORCPT ); Thu, 9 Jul 2015 17:06:03 -0400 Date: Thu, 9 Jul 2015 14:06:02 -0700 From: Andrew Morton To: Gang He 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 Message-Id: <20150709140602.eafbc5a3b7660a6c7588e1b6@linux-foundation.org> In-Reply-To: <1435123461-3525-1-git-send-email-ghe@suse.com> References: <1435123461-3525-1-git-send-email-ghe@suse.com> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1074 Lines: 24 On Wed, 24 Jun 2015 13:24:17 +0800 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 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/