From: Jan Kara <jack@suse.cz>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
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: Fri, 22 Jan 2016 10:36:26 +0100 [thread overview]
Message-ID: <20160122093626.GD16898@quack.suse.cz> (raw)
In-Reply-To: <56A11231.8040801@suse.de>
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...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2016-01-22 9:36 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 ` Jan Kara [this message]
2016-01-22 12:04 ` [Lsf-pc] " 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=20160122093626.GD16898@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=rgoldwyn@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).