public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Freeman <rich@thefreemanclan.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] What should the swap size be for 4G ram?
Date: Sat, 22 Sep 2007 13:23:39 -0400	[thread overview]
Message-ID: <46F54F9B.6090006@thefreemanclan.net> (raw)
In-Reply-To: <200709221722.31174.volker.armin.hemmann@tu-clausthal.de>

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Volker Armin Hemmann wrote:
> why? zfs is slow and is mixing things that should be in different layers. One 
> argument against reiser4 always was 'it violates the layering' - well this is 
> even more true for zfs.
> 

If you can suggest a filesystem that has full redundancy and uses all my
disk space optimally I'll be happy to use it.  :)  Ideally I'd prefer
not to have to carefully map and partition my drives and be able to add
space on a whim, but maybe that is asking too much.  But ZFS allows all
of this. RAID5 does not.

In theory ZFS also has much better write performance than RAID5 -
because it doesn't need to read stripe before writing them most of the time.

Sure, it is a layering violation, but there really isn't any way to
implement this sort of scheme using layers.  If you separate the raid
layer from the FS layer then the raid has no idea whether a given block
of disk is safe to overwrite or not - so it has to read stripes before
writing them.  So, while I do like the flexibility of running any
filesystem on top of any lvm/md scheme I'll live with the inflexibility
if it gives me more capability.

As far as performance goes - ZFS is pretty immature - I'm sure it will
only improve.  Especially considering it only has the most minimal
support for linux right now.  Obviously I'd wait until something more
robust is available...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFG9U+YG4/rWKZmVWkRAhM/AKC7oL99LD6rVBYWZT8FKX+3TfLGfQCgkToP
JO0yxcMT1ptvRbhN35GxNvk=
=Srvy
-----END PGP SIGNATURE-----

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 4101 bytes --]

  parent reply	other threads:[~2007-09-22 17:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-22  3:16 [gentoo-amd64] What should the swap size be for 4G ram? P.V.Anthony
2007-09-22  3:22 ` P.V.Anthony
2007-09-22 15:15   ` Richard Freeman
2007-09-22 15:22     ` Volker Armin Hemmann
2007-09-22 16:24       ` B Vance
2007-09-22 17:23       ` Richard Freeman [this message]
2007-09-22 17:23     ` [gentoo-amd64] " Duncan
2007-09-22 20:22       ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46F54F9B.6090006@thefreemanclan.net \
    --to=rich@thefreemanclan.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox