From: Ryusuke Konishi <ryusuke@osrg.net>
To: raa.lkml@gmail.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: Fri, 13 Mar 2009 19:04:18 +0900 (JST) [thread overview]
Message-ID: <20090313.190418.110778375.ryusuke@osrg.net> (raw)
In-Reply-To: <81b0412b0903130105y2f9c2430iabaab26d6a8e8188@mail.gmail.com>
Hi!
On Fri, 13 Mar 2009 09:05:53 +0100, Alex Riesen wrote:
> 2009/3/10 Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>:
> >
> > # mount -t nilfs2 -r -o cp=33339 /dev/sdb1 /snap
> > (mount the snapshot, then it will become accessible on the mount=
point)
>
> Is it possible to mount a snapshot rw to make it a branch?
No, the writable snapshot is not supported.
( So, a readonly option appears in the example. )
Maybe the current design is unfit for efficient branching because
nilfs identifies checkpoints with linear numbers and manages lifetime
of each on-disk block with a range of the numbers.
We might be able to add a feature like replacing the latest filesystem
state with a past snapshot, but it's not yet determined.
Cheers,
Ryusuke
prev parent reply other threads:[~2009-03-13 10:04 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
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 [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=20090313.190418.110778375.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=raa.lkml@gmail.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