On January 28, 2007 4:59:48 PM +0100 Pawel Jakub Dawidek <[EMAIL PROTECTED]>
wrote:
On Fri, Jan 26, 2007 at 06:08:50PM -0800, Darren Dunham wrote:
> 3. I created file system with huge amount of data, where most of the
> data is read-only. I change my server from intel to sparc64 machine.
> Adaptive endianess only change byte order to native on write and
> because file system is mostly read-only, it'll need to byteswap all
> the time. And here comes 'zfs rewrite'!
It's only the metadata that is modified anyway, not the file data. I
would hope that this could be done more easily than a full tree rewrite
(and again the issue with snapshots). Also, the overhead there probably
isn't going to be very high (since the metadata will be cached in most
cases).
Agreed. Probably in this case there should be rewrite-only-metadata
mode. I agree the overhead is probably not high, but on the other hand,
I'm quite sure there are workload, which will see the difference, eg.
'find / -name something'.
I'd imagine even for that it wouldn't matter. The I/O time will dwarf
any time spent byte-swapping. Easily tested though. Make sure you
set atime=off so that your find isn't causing write I/O.
-frank
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
