From owner-freebsd-fs@FreeBSD.ORG  Thu May 17 20:50:13 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 70C1E10657FC
	for <freebsd-fs@FreeBSD.org>; Thu, 17 May 2012 20:50:13 +0000 (UTC)
	(envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
	by mx1.freebsd.org (Postfix) with ESMTP id 5239B8FC1C
	for <freebsd-fs@FreeBSD.org>; Thu, 17 May 2012 20:50:13 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id q4HKo6hK000183;
	Thu, 17 May 2012 13:50:09 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <201205172050.q4HKo6hK000183@gw.catspoiler.org>
Date: Thu, 17 May 2012 13:50:06 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: gjb@semihalf.com
In-Reply-To: <4FB4EABA.702@semihalf.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=iso-8859-1
Cc: freebsd-fs@FreeBSD.org
Subject: Re: NAND Framework in HEAD.
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 20:50:13 -0000

On 17 May, Grzegorz Bernacki wrote:

> NAND FS adopts log-structured approach and some parts of its internal 
> design are derived from the new implementation of the log-structured 
> file system (NILFS), with some concepts rooting in the original (now 
> legacy) BSD log-structured file system (LFS).
> 
> The NAND FS has the following major features:
>    - Hard links
>    - Symbolic links
>    - Case-sensitive, case-preserving
>    - Snapshots
>      ? No limit on the number of snapshots (only volume-limited)
>      ? Mountable as read-only file systems
>      ? Simultaneously mountable (there can be a writable mount concurrently
>        mixed with a number of read-only snapshots)
>    - Redundant super block
>    - Metadata
>      ? POSIX file permissions
>      ? Creation timestamps
>      ? Last content modification timestamps
>      ? Last metadata change timestamps
>      ? Checksum / ECC

Any thoughts on how well NAND FS might work on SSDs as compared to
something like UFS, which isn't aware of the properties of the
underlying storage?  I would think that avoiding random block overwrites
would help performance and device lifetime.

[Cc: trimmed]