From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:34762 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759902AbcAURPg (ORCPT ); Thu, 21 Jan 2016 12:15:36 -0500 To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org From: Goldwyn Rodrigues Subject: [LSF/MM TOPIC] Online filesystem check framework Message-ID: <56A11231.8040801@suse.de> Date: Thu, 21 Jan 2016 22:45:29 +0530 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Topic: Generic Online filesystem Check framework Motivation: + Better uptime - Filesystems turn read-only at the first error encountered and it may block critical applications which have not encountered the error. + Unmountable Filesystems - Some filesystems such as clustered filesystem may not be unmountable because they are used by too many computers to be taken offline. + Autofix - may sound dangerous as fixing is without user intervention, but an option may help admins which are looking for a good uptime. + Logic inbuilt - most logic of access to filesystem is already in the filesystem driver. The fix/check would make use of existing functionality. Framework would be around providing a generic interface framework which would use inode numbers as the basic unit to check or fix. Other metadata may need special parameters. Userspace scripts will issue check/fixes to the system, which may/may not be driven by My other interests include VFS, access control and security, and future plans with the VFS and storage subsystems. I am also interested in multi-device arrays such as MD and DM. -- Goldwyn