Linux NILFS development
 help / color / mirror / Atom feed
From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [CFD] disk format fixing
Date: Sun, 16 May 2010 23:42:31 +0900	[thread overview]
Message-ID: <87pr0v7vs8.wl%jir@sekiba.com> (raw)
In-Reply-To: <87aash3rrm.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>

Hi,

I'd like to summarize the comments so far for disk fomat fix.
Please correct it if it's wrong or missing something.


I've started this thread to fix disk format of nilfs2 at the point
everybody thinks it's ok, strip "experimental", encourage developing
user land tools and different implementation like on NetBSD.

So far, we have been talking disk format from two aspects,
spuer block and rest of disk.  That's simply because most of user land tools
care only super block and rest of disk are much more controversial
than super block.  I'd like to summarize from those aspects.

- Super block format

Super blocks are frequently updated hotspot of nilfs2.  This is not good
for low-end flash device for wearing point of view.  To address this problem,
suggested introducing new mount option that makes less updates super blocks.

At this point, super block format itself is unchanged, still oloder
nilfs implementation can find correct latest log in case of unclean mount.

- Rest of disk

* directory indexing
There is long term controversial discussion about directory indexing.
One is on memory indexing, the other is on disk indexing.  We have not
reached a resolution, but at least agreed "unchange for now".
So, disk format point of view, it'll be fixed for nilfs2.
However it is a subject to change for future nilfs2 or nilfs3 or so.

~~

There are more missing features that should be in a modern filesystem,
like xattr or posix acls, check ToDo list in following url:
http://www.nilfs.org/en/current_status.html

You may not have to know disk format but if you feel functions which 
are not in nilfs2, but mandatory to support, please state so.
Then we can start that the how those functions can be implmented in nilfs2
from disk format point of view.  Otherwise, any functions that requires disk
format change will be not supported in near future or forever "experimental".

thanks,

regards,
-- 
Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2010-05-16 14:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 15:54 [CFD] disk format fixing Jiro SEKIBA
     [not found] ` <87aash3rrm.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-05-03 19:35   ` Jay Carlson
     [not found]     ` <7E6B7E93-FCB4-4E4C-AF4F-BEA8D8FE1F20-Nqdcz63CPQY@public.gmane.org>
2010-05-04 12:02       ` Reinoud Zandijk
     [not found]         ` <20100504120222.GA1132-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2010-05-04 14:01           ` Ryusuke Konishi
     [not found]             ` <20100504.230135.205087691.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-05 15:10               ` Jiro SEKIBA
     [not found]                 ` <8739y675aa.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-05-05 18:23                   ` Ryusuke Konishi
     [not found]                     ` <20100506.032327.203276062.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-09 16:45                       ` Jiro SEKIBA
     [not found]                         ` <87aas9hvm8.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-05-09 18:29                           ` Ryusuke Konishi
     [not found]                             ` <20100510.032922.158554882.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-11 14:43                               ` Jiro SEKIBA
2010-05-04 12:06   ` Reinoud Zandijk
     [not found]     ` <20100504120623.GB1132-bVHBekiX4bNgoMqBc1r0ESegHCQxtGRMHZ5vskTnxNA@public.gmane.org>
2010-05-05 15:19       ` Jiro SEKIBA
2010-05-04 14:38   ` Ryusuke Konishi
2010-05-16 14:42   ` Jiro SEKIBA [this message]
     [not found]     ` <87pr0v7vs8.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2010-05-16 17:25       ` Ryusuke Konishi
     [not found]         ` <20100517.022540.171394303.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-05-18 14:13           ` Jiro SEKIBA

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=87pr0v7vs8.wl%jir@sekiba.com \
    --to=jir-hfpbi5wx9j54eiagz67ipq@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox