All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: [LSF/MM TOPIC] Online filesystem check framework
Date: Thu, 21 Jan 2016 22:45:29 +0530	[thread overview]
Message-ID: <56A11231.8040801@suse.de> (raw)


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

             reply	other threads:[~2016-01-21 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-21 17:15 Goldwyn Rodrigues [this message]
2016-01-22  9:36 ` [Lsf-pc] [LSF/MM TOPIC] Online filesystem check framework Jan Kara
2016-01-22 12:04   ` Dave Chinner
2016-01-25 18:37   ` Goldwyn Rodrigues

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=56A11231.8040801@suse.de \
    --to=rgoldwyn@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.