Hi,
On Sun, 22 Jul 2012 19:13:01 +0400, Vyacheslav Dubeyko wrote:
> Hi,
> 
> This patch set adds skeleton of fsck.nilfs2 utility into nilfs-utils package. 
> Currently, fsck.nilfs2 only try to check presence of primary and secondary 
> superblocks. It checks magic signature in superblock.
> 
> With the best regards,
> Vyacheslav Dubeyko.

I'm planning to look this patchset weekend.

One question is about your plan for proceeding this task.

Implementing fsck looks a tough task since NILFS has history of data
and meta-data as well as the current file system structures, and correcting
filesystem looks to need log write in user-land, which is not yet realized.

So, taking a step-by-step approach seems essential.

In this sense, did you design the skelton, thinking of further steps?
If you have some strategy to accomplish this task, I'd like to hear
that.

My concern for this is avoiding rework of the future.

I'm very thankful for your challenges.

With regards,
Ryusuke Konishi

> --
>  configure.ac     |    3 ++-
>  sbin/Makefile.am |    2 +-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
>  sbin/fsck/Makefile.am        |   13 ++
>  sbin/fsck/fsck_messages.c    |  254 ++++++++++++++++++++++++
>  sbin/fsck/fsck_messages.def  |   62 ++++++
>  sbin/fsck/fsck_messages.h    |  110 +++++++++++
>  sbin/fsck/fsck_nilfs2.c      |  379 +++++++++++++++++++++++++++++++++++
>  sbin/fsck/fsck_nilfs2.h      |   37 ++++
>  sbin/fsck/fsck_raw_ops.c     |  413 +++++++++++++++++++++++++++++++++++++++
>  sbin/fsck/fsck_raw_ops.h     |   46 +++++
>  sbin/fsck/nilfs_superblock.c |  445 
> ++++++++++++++++++++++++++++++++++++++++++
>  sbin/fsck/nilfs_superblock.h |   48 +++++
>  10 files changed, 1807 insertions(+), 0 deletions(-)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
> the body of a message to [email protected]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to