Date: Sun, 06 Jan 2008 18:28:30 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: When will ZFS become stable? Message-ID: <flr340$mum$1@ger.gmane.org> In-Reply-To: <20080106170452.L105@fledge.watson.org> References: <fll63b$j1c$1@ger.gmane.org> <20080106141157.I105@fledge.watson.org> <flr0np$euj$2@ger.gmane.org> <20080106170452.L105@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig601868FFD7E993E6262A8244 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Sun, 6 Jan 2008, Ivan Voras wrote: >> Last I heard, rsync didn't crash Solaris on ZFS :) >=20 > My admittedly second-hand understanding is that ZFS shows similarly=20 > gratuitous memory use on both Mac OS X and Solaris. One advantage=20 > Solaris has is that it runs primarily on expensive 64-bit servers with = > lots of memory. Part of the problem on FreeBSD is that people run ZFS = > on sytems with 32-bit CPUs and a lot less memory. It could be that ZFS= =20 > should be enforcing higher minimum hardware requirements to mount (i.e.= ,=20 > refusing to run on systems with 32-bit address spaces or <4gb of memory= =20 > and inadequate tuning). Solaris nowadays refuses to install on anything without at least 1 GB of = memory. I'm all for ZFS refusing to run on inadequatly tuned hardware,=20 but apparently there's no algorithmic way to say what *is* adequately=20 tuned, except for "try X and if it crashes, try Y, repeat as necessary". The reason why I'm arguing this topic is that it isn't a matter of=20 tuning like "it will run slowly if you don't tune it" - it's more like=20 "it won't run at all if you don't go through the laborious=20 trial-and-error process of tuning it, including patching your kernel and = running a non-GENERIC configuration". --------------enig601868FFD7E993E6262A8244 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHgQ+/ldnAQVacBcgRAtnAAKCtMumii9wevIzasHr8NZ6x5aGQ2ACcDmBf Nqzn2r1T/d1ngFr8i4tyZHU= =PAma -----END PGP SIGNATURE----- --------------enig601868FFD7E993E6262A8244--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?flr340$mum$1>