All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: Jan Kara <jack@suse.cz>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Online filesystem check framework
Date: Tue, 26 Jan 2016 00:07:14 +0530	[thread overview]
Message-ID: <56A66B5A.2020804@suse.de> (raw)
In-Reply-To: <20160122093626.GD16898@quack.suse.cz>



On 01/22/2016 03:06 PM, Jan Kara wrote:
> Hello,
>
> On Thu 21-01-16 22:45:29, Goldwyn Rodrigues wrote:
>> 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
>
> Well, this is a very difficult topic so I think we need some concrete
> proposal and ideally some RFC code about what you think needs to be done to
> make online fsck possible. Without that it will be just a useless
> handwaving since I don't think anybody is able to come up with a decent
> proposal during that half an hour session...


Yes, I do have something more than this in mind, and I will come up with 
an RFC and hopefully some code. I will try and post it by the deadline 
of Feb 11.



-- 
Goldwyn

      parent reply	other threads:[~2016-01-25 18:37 UTC|newest]

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

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=56A66B5A.2020804@suse.de \
    --to=rgoldwyn@suse.de \
    --cc=jack@suse.cz \
    --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.