Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [CFD] disk format fixing
Date: Tue, 04 May 2010 23:38:36 +0900 (JST)	[thread overview]
Message-ID: <20100504.233836.131490856.ryusuke@osrg.net> (raw)
In-Reply-To: <87aash3rrm.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>

On Tue, 04 May 2010 00:54:21 +0900, Jiro SEKIBA wrote:
> Hi,
> 
> It's been almost a year that nilfs2 has been merged into mainline kernel
> since 2.6.30, which is released in Jun 2009.  Yet, it still shows warnings
> that "The NILFS on-disk format may change at any time".
> 
> It still remains controversial argument, like directory indexing
> or atime support, xattr support and so on.  However, I'd like to
> make the target clear that when the above message can be taken away.
> 
> By fixing disk format, we might go forward to contribute more useful
> disk utilities like GNU pared.  Some of those user land utilities require
> just reading super block (or blocks) to identify what the filesystem is
> in the specified partition.  Therefore it would be good starting point to
> declare superblock format which ensure that upper/lower compatibilities.
> 
> In addition to superblock format, over all disk format must be fixed
> somehow everybody thinks "it's ok".

Thank you for this proposal.

I think the warning should be removed much earlier, but at least, it's
preferable that the decision is based on some consensus.

Sekiba-san, could you become the facilitator of this discussion?

I think we should take a step-by-step approach.

I agree freezing superblock format is a good milestone for it.

Preferably, it should be included for 2.6.35.

With regards,
Ryusuke Konishi
--
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-04 14:38 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 [this message]
2010-05-16 14:42   ` Jiro SEKIBA
     [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=20100504.233836.131490856.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=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