Linux NILFS development
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: NILFS specs
Date: Fri, 04 Jul 2008 01:38:26 +0900 (JST)	[thread overview]
Message-ID: <20080704.013826.27467526.ryusuke@osrg.net> (raw)
In-Reply-To: <20080703151041.GA24860-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>

Hello,

On Thu, 3 Jul 2008 17:10:41 +0200, Reinoud Zandijk wrote:
> Dear Gergely,
> 
> On Thu, Jul 03, 2008 at 03:14:16PM +0200, Gergely G?bor wrote:
> > On Thursday 03 July 2008 13:44:28 Reinoud Zandijk wrote:
> > > as a NetBSD developer i recently stumbled on NilFS and wondered where i
> > > could find the specs of the disc format to better understand the disc
> > > format. Is there a specification document around? Or should i look into the
> > > sources for it?
> >
> > Are you planning to port nifs2 to NetBSD? That would be great news!

and sounds tough. :-)

> Well that depends! :) depends on how much info i can get on the FS since 
> i'll have to rewrite most of it for various reasons :-/ I am currently 
> battling UDF still and its far from finished but i'd like to dig into nilfs 
> since i like its ideas.
>
> It'd be a shame if i have to develop my own version of nilfs and make them 
> incompatible :-(

Sorry for inconvenience.
I recognize it's one of what needs to be dissolved, and one of my colleagues
is working on writing the paper of NILFS2, but still not lead to publish it.

Though the documents of NILFS version 1 are available from
http://www.nilfs.org/en/links.html, the disk format was fairly changed
on version 2.  Especially the disk address translation file (DAT), which
was introduced in NILFS2 to implement garbage collection, made significant
difference among these two versions.

If you get tired of waiting, I recommend you to see ``nilfs_fs.h'' because
every definition around on-disk information is gathered in this header.

Best regards,
Ryusuke Konishi

      parent reply	other threads:[~2008-07-03 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 11:44 NILFS specs Reinoud Zandijk
     [not found] ` <20080703114428.GA22708-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-07-03 13:14   ` Gergely Gábor
     [not found]     ` <200807031514.21594.elentirmo.gilgalad-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-07-03 15:10       ` Reinoud Zandijk
     [not found]         ` <20080703151041.GA24860-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-07-03 16:38           ` Ryusuke Konishi [this message]

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=20080704.013826.27467526.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@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