Super Root Block

Super Root Block

[Assaf Weizman]

Hello,
Could you please explain a few theoretical questions:
a. What's the meaning/usage of the "Super Root Block"?
b. in the Readme (v2) file it's described as "an optional super root
block (SR)". So as optional element,  who chooses to whether to
activate\use it or not?

Thanks a lot. this is a very interesting file system.

Best regards
Assaf Weizman
--
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

Re: Super Root Block

[Ryusuke Konishi]

Hi,
On Mon, 8 Mar 2010 10:59:44 +0200, Assaf Weizman wrote:
> Hello,
> Could you please explain a few theoretical questions:
> a. What's the meaning/usage of the "Super Root Block"?
> b. in the Readme (v2) file it's described as "an optional super root
> block (SR)". So as optional element,  who chooses to whether to
> activate\use it or not?

The super root block contains inodes of checkpoint file (cpfile),
segment usage file (sufile), and disk address translation (DAT) file.

It represents the top of metadata hierarchy of NILFS at a time point.
For the metadata hierarchy, please see the page 9 of the slides:

 http://www.nilfs.org/papers/jls2009-nilfs.pdf 


I think the term "optional" in the readme looks confusing.

In nilfs, if a series of logs makes a new checkpoint, it essentially
ends with a super root block.  Otherwise, it does not entail the super
root block (there is a variant of log series used for synchronous data
write).

> Thanks a lot. this is a very interesting file system.
> 
> Best regards
> Assaf Weizman

Thank you.  I think the above slides would be helpful than the readme
file.

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

Re: Super Root Block

[Assaf Weizman]

Thank you very much! Mr. Konishi.

Best wishes
Assaf Weizman

On Mon, Mar 8, 2010 at 12:08 PM, Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org> wrote:
>
> Hi,
> On Mon, 8 Mar 2010 10:59:44 +0200, Assaf Weizman wrote:
> > Hello,
> > Could you please explain a few theoretical questions:
> > a. What's the meaning/usage of the "Super Root Block"?
> > b. in the Readme (v2) file it's described as "an optional super root
> > block (SR)". So as optional element,  who chooses to whether to
> > activate\use it or not?
>
> The super root block contains inodes of checkpoint file (cpfile),
> segment usage file (sufile), and disk address translation (DAT) file.
>
> It represents the top of metadata hierarchy of NILFS at a time point.
> For the metadata hierarchy, please see the page 9 of the slides:
>
>  http://www.nilfs.org/papers/jls2009-nilfs.pdf
>
>
> I think the term "optional" in the readme looks confusing.
>
> In nilfs, if a series of logs makes a new checkpoint, it essentially
> ends with a super root block.  Otherwise, it does not entail the super
> root block (there is a variant of log series used for synchronous data
> write).
>
> > Thanks a lot. this is a very interesting file system.
> >
> > Best regards
> > Assaf Weizman
>
> Thank you.  I think the above slides would be helpful than the readme
> file.
>
> 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