Date: Fri, 13 Mar 2009 19:04:18 +0900 (JST)
Message-Id: <20090313.190418.110778375.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
From: Ryusuke Konishi <ryusuke@osrg.net>
In-Reply-To: <81b0412b0903130105y2f9c2430iabaab26d6a8e8188@mail.gmail.com>
References: <20090311.015542.118514963.ryusuke@osrg.net>
	<81b0412b0903130105y2f9c2430iabaab26d6a8e8188@mail.gmail.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 992
Lines: 27

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/