From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Q2489-0006aQ-Vy for garchives@archives.gentoo.org; Tue, 22 Mar 2011 16:08:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C3BEC1C083; Tue, 22 Mar 2011 16:06:53 +0000 (UTC) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by pigeon.gentoo.org (Postfix) with ESMTP id 91BD71C083 for ; Tue, 22 Mar 2011 16:06:53 +0000 (UTC) Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id 4B1E320532 for ; Tue, 22 Mar 2011 12:06:53 -0400 (EDT) Received: from frontend2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 22 Mar 2011 12:06:53 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:mime-version:to:subject:references:in-reply-to:content-type; s=smtpout; bh=83NQHhmkc4E6FFStcoJ90y3rgwI=; b=rX7DzIZdAId9Lh8xPaH7wHMIZ0/GceD+uWoW42+zkWSEzqakPSWZ78NP2FsahvEQT0M7MEoIYRXHxrOIhf9M1ZqthEE8ILoHSRM9dTft3ViOExMGAP161LamG2wrVULlVvf4VwsS+ptCl2FArwZKzieO/Wb2qhF6UbLxfxU+/nc= X-Sasl-enc: ED1VLfdlGQNNJiLTCq1SNBTuzHZF/Ab9soziEfCJsiIz 1300810012 Received: from [192.168.5.18] (serv.binarywings.net [83.169.5.6]) by mail.messagingengine.com (Postfix) with ESMTPSA id E930E447889 for ; Tue, 22 Mar 2011 12:06:51 -0400 (EDT) Message-ID: <4D88C8C7.6010506@binarywings.net> Date: Tue, 22 Mar 2011 17:05:27 +0100 From: Florian Philipp User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110313 Lightning/1.0b3pre Thunderbird/3.1.9 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] the best filesystem for server: XFS or JFS (or?) References: <4D87A7C6.1060502@gmail.com> <4D87C89D.7090007@gmail.com> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig57D18666AFD4E4C9F8381E07" X-Archives-Salt: X-Archives-Hash: 7b5125af070dfb2f2631d14fa3761a0d This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig57D18666AFD4E4C9F8381E07 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 22.03.2011 09:13, schrieb Mr. Jarry: > Thanks for replies. As I had expected, they brought even more > uncertainty then I had before... :-) >=20 > ext3/4: > I excluded them because as I understand, they do not support > snapshots (only with lvm, which I do not use, and I've hreard > snapshots in lvm are not very effective, or something like that). > Next minus-point, I tried resizing of ext3/lvm once in the past > and remember it was a real pain in a**... >=20 Neil already pointed out that resizing is plain easy. Increasing the size online is a matter of seconds. Shrinking needs to be done offline after an `e2fsck -f` but is no problem, either. > reiserfs/reiser4: > Future of these fs seems to be somehow vague, at least to me. > And I do not know if it can handle snaphosts and resizing. >=20 Reiserfs-3 supports increasing the size but not shrinking (AFAIK). Performance characteristics are similar to Ext3 in this regard. > xfs & power-off: > I have always thought, journaling is there to prevent data > loss during unexpected power-off. And now I read I could > loose data even with journaled fs...? >=20 Journalling is better suited for system crashes than power failures. Things get especially ugly when you think about write caches in HDDs or RAID controllers. Additionally, the main purpose of journalling is to protect the file system, not the data. Normally, journals only contain metadata changes like space allocations to files but not the actual data written to it. Even good old Ext3 might put random junk at the end of your files when it is mounted with journal=3Dwriteback during a crash. This is basically a speed/security tradeoff. When you read up about the various journal options for Ext3, you will understand it better. > jfs & power-off: > the same. How is it possible, I could loose data with such > a mature journaled filesystem during power-off? >=20 > btrfs: > never heard of it. Is it stable enough to be used? I just > checkt man-page of "mount", and it does not show btrfs > as supported filesystem... > Wikipedia has information about it. Basically, it will be replacement of Ext4. Hope this helps, Florian Philipp --------------enig57D18666AFD4E4C9F8381E07 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2IyMwACgkQqs4uOUlOuU9s5gCcCjdjhmCU+CxbyhscRldYZ/65 XSwAnRe+1/F8d+msBBnOJXmeyE5uyWxv =Zf5W -----END PGP SIGNATURE----- --------------enig57D18666AFD4E4C9F8381E07--