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
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html