[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060801092514.GB2974@merlin.emma.line.org>
Date: Tue, 1 Aug 2006 11:25:14 +0200
From: Matthias Andree <matthias.andree@....de>
To: Avi Kivity <avi@...o.co.il>
Cc: Theodore Tso <tytso@....edu>,
David Lang <dlang@...italinsight.com>,
David Masover <ninja@...phack.com>, tdwebste2@...oo.com,
Nate Diller <nate.diller@...il.com>,
Adrian Ulrich <reiser4@...nkenlights.ch>,
"Horst H. von Brand" <vonbrand@....utfsm.cl>, ipso@...ppymail.ca,
reiser@...esys.com, lkml@...productions.com, jeff@...zik.org,
linux-kernel@...r.kernel.org, reiserfs-list@...esys.com
Subject: Re: Solaris ZFS on Linux [Was: Re: the " 'official' point of view"expressed by kernelnewbies.org regarding reiser4 inclusion]
On Tue, 01 Aug 2006, Avi Kivity wrote:
> There's no reason to repack *all* of the data. Many workloads write and
> delete whole files, so file data should be contiguous. The repacker
> would only need to move metadata and small files.
Move small files? What for?
Even if it is "only" moving metadata, it is not different from what ext3
or xfs are doing today (rewriting metadata from the intent log or block
journal to the final location).
The UFS+softupdates from the BSD world looks pretty good at avoiding
unnecessary writes (at the expense of a long-running but nice background
fsck after a crash, which is however easy on the I/O as of recent FreeBSD
versions). Which was their main point against logging/journaling BTW,
but they are porting XFS as well to save those that need instant
complete recovery.
--
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists