From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GeD7l-00037Y-7p for garchives@archives.gentoo.org; Sun, 29 Oct 2006 16:03:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9TFwMxs011396; Sun, 29 Oct 2006 15:58:22 GMT Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9TFtVjH026574 for ; Sun, 29 Oct 2006 15:55:31 GMT Received: by nf-out-0910.google.com with SMTP id p46so2778651nfa for ; Sun, 29 Oct 2006 07:55:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Gbl5AuXfWziC4lwjEOnJOEXvW/b5k6CV2Ue7UO0a+x0QhcgPDv9oZA12+Lup+1RfwxR9wDFBCY4rKFrOP9JLmQ1+QGddaE7rL51KDg4WAhnLTWl+zHQAQGindl7gSTNqFXW9fMFm/M/G7Ycow1sPM/SwQcw2uaI5pK4Fp96QO0o= Received: by 10.82.139.17 with SMTP id m17mr256386bud; Sun, 29 Oct 2006 07:55:31 -0800 (PST) Received: by 10.82.177.12 with HTTP; Sun, 29 Oct 2006 07:55:31 -0800 (PST) Message-ID: Date: Sun, 29 Oct 2006 08:55:31 -0700 From: "Joshua Schmidlkofer" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] BIG reiserfs problem In-Reply-To: <200610281121.25785.nbensa@gmx.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200610281121.25785.nbensa@gmx.net> X-Archives-Salt: 463973c3-153a-48cc-9975-3d1d4aa6ddec X-Archives-Hash: 373d4dc31eeaa5777215b905e5c981ae Dude - I use xfs w/o a UPS for desktops and laptops. I use it on servers with RAID and with UPS protection. I also keep good backups for the servers. I have been using XFS since _just_ _after_ it came to Linux. I have used XFS on several hundred systems (which I have been responsible for). I have, to date, lost two filesystems. a. 2000 - I lost a filesystem when I was running a CVS kernel. *hhahaha* yeah, it was ugly, during the 2.4 kernel of pain days. b. 2006 - hardware slowly corrupted an FS. Some files wouldn't read, and we had wierd problems, (but good backups). After firmware updates problems got stranger, and xfs_repair finished the job. I blame the hardware. I have read the list, and seen the problems. I don' t know what I do that makes XFS succeed, but It really does work well. The first filesystem I ever tried with JFS failed. I had weird errors, and strange messages. I tried the repair tools, but they crashed. Then, I posted to the LKML. No one replied, or was interested. I left JFS, and returned to XFS. I have run into a few strange bugs with XFS, but in every case I found the mailing list and IRC very responsive and I was able to return the servers to operation. Twice those have been caused by either 2.4 or XFS. Once or twice it was several compound power outages. What really kills XFS is _NOT_ power outages - it is out-of-order commits. When the drives re-order the commits, it really can f-up the drive. The data portion of the disk is updated and the journal isn't. Then, if you have a crash, you are in some pretty sh*t. That's why write barriers are so important. Use what you want, but don't misunderstand XFS - as many people here clearly do. It's a good FS, but it is sensitive to hardware problems. By problems I mean: dying disks (which will kill anyone), faulty commit order for data vs. journal (which probably affects all of the journaling FSs as well), silent corruption, faulty RAM, and last but not least DMA problems. If you have a drive that commits out of order, and you are prone to power problems: USE EXT2 - it is , bar none, the SAFEST filesystem in that case. I do use it on a couple systems with those exact problems. (And a couple of low-memory systems, journalling sucks up resources). I have not lost an ext2 fs yet in either of those cases. Sure, the systems occasionally experience some meessed up files, but never the whole FS, and replacing a library or binary is /not/ /that/ /tough/. Good Luck, Joshua -- gentoo-user@gentoo.org mailing list