[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44CF2112.8040202@argo.co.il>
Date: Tue, 01 Aug 2006 12:38:26 +0300
From: Avi Kivity <avi@...o.co.il>
To: Matthias Andree <matthias.andree@....de>
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]
Matthias Andree wrote:
>
> 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?
>
WAFL-style filesystems like contiguous space, so if small files are
scattered in otherwise free space, the repacker should free them.
> 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).
>
There is no need to repack all metadata; only that which helps in
creating free space.
For example: if you untar a source tree you'd get mixed metadata and
small file data packed together, but there's no need to repack that data.
--
error compiling committee.c: too many arguments to function
-
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