From: Ryusuke Konishi <ryusuke@osrg.net>
To: sitsofe@yahoo.com
Cc: konishi.ryusuke@lab.ntt.co.jp, akpm@linux-foundation.org,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Asking for inclusion of nilfs2 in the mainline kernel
Date: Wed, 11 Mar 2009 03:54:00 +0900 (JST) [thread overview]
Message-ID: <20090311.035400.12547305.ryusuke@osrg.net> (raw)
In-Reply-To: <20090310174627.GA10667@silver.sucs.org>
Hi,
On Tue, 10 Mar 2009 17:46:27 +0000, Sitsofe Wheeler wrote:
> Hello,
>
> On Wed, Mar 11, 2009 at 01:55:42AM +0900, Ryusuke Konishi wrote:
> > # lscp
> > (list checkpoints)
> >
> > CNO DATE TIME MODE FLG NBLKINC ICNT
> > 33338 2009-03-08 14:45:49 cp - 11 3
> > 33339 2009-03-08 14:50:22 cp - 200523 81
> > 33340 2009-03-08 20:40:34 cp - 136 61
> > 33341 2009-03-08 20:41:20 cp - 187666 1604
> > 33342 2009-03-08 20:41:42 cp - 51 1634
> > ...
>
> Is there a cheaty way to get at checkpointed files (and the list of
> checkpoints) through some sort of magic dot directory system (so you
> wouldn't need the userland tools and the remounting)?
No, we don't give the special namespace extension to nilfs2.
Instead, we have adopted out-of-filesystem solution, that is, using
autofs to present checkpoints on namespace outside nilfs.
Autofs is useful to presents many snapshots or checkpoints
automatically, and it allows flexible naming rules.
Maybe we can natively support the magic dot directory, and we may do
that if many users demand it or we confront some kind of scalability
issue. But, so far it seems to work well enough.
Regards,
Ryusuke
next prev parent reply other threads:[~2009-03-10 18:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 16:55 Asking for inclusion of nilfs2 in the mainline kernel Ryusuke Konishi
2009-03-10 17:46 ` Sitsofe Wheeler
2009-03-10 18:54 ` Ryusuke Konishi [this message]
2009-03-10 18:25 ` Greg KH
2009-03-10 19:23 ` Ryusuke Konishi
2009-03-10 22:54 ` Andrew Morton
2009-03-11 8:35 ` Ryusuke Konishi
2009-03-13 7:21 ` Ryusuke Konishi
2009-03-13 8:05 ` Alex Riesen
2009-03-13 10:04 ` Ryusuke Konishi
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=20090311.035400.12547305.ryusuke@osrg.net \
--to=ryusuke@osrg.net \
--cc=akpm@linux-foundation.org \
--cc=hch@lst.de \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sitsofe@yahoo.com \
/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