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 <gentoo-user+bounces-53840-garchives=archives.gentoo.org@gentoo.org>)
id 1Gdru1-00046S-0c
for garchives@archives.gentoo.org; Sat, 28 Oct 2006 17:23:25 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k9SHJ2tx032536;
Sat, 28 Oct 2006 17:19:02 GMT
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171])
by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k9SHGiBE024653
for <gentoo-user@lists.gentoo.org>; Sat, 28 Oct 2006 17:16:44 GMT
Received: by ug-out-1314.google.com with SMTP id p27so903427ugc
for <gentoo-user@lists.gentoo.org>; Sat, 28 Oct 2006 10:16:44 -0700 (PDT)
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:references;
b=YACIKAFGfc9PU8lbhb0F3dqSfNjAnM8rPnn1ymCep/EdWITn13Km4eGIOZI/VoJd+7uJU4SKmKAPmoWz07WKq8NVbm+R0NG0iJJcDk7A2k5wlxJXwmn1IMWbR6GZoWILo52FX9udH+TZRFGBk+34/cZDuWodVJ8rDfwOawxeUbs=
Received: by 10.67.103.7 with SMTP id f7mr1457241ugm;
Sat, 28 Oct 2006 10:16:44 -0700 (PDT)
Received: by 10.66.221.1 with HTTP; Sat, 28 Oct 2006 10:16:44 -0700 (PDT)
Message-ID: <d03887390610281016k1454daf0wac2ca0a6db3effcc@mail.gmail.com>
Date: Sat, 28 Oct 2006 17:16:44 +0000
From: CapSel <capsel@gmail.com>
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: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_92922_30569948.1162055804001"
References: <d03887390610280316t38f83b1fi778dc46572d3a463@mail.gmail.com>
<200610281121.25785.nbensa@gmx.net>
X-Archives-Salt: c876d2ad-1cbb-4103-8a97-fbe40da1b23e
X-Archives-Hash: 20d0cc6c70ff235ec4e7874dadfd6e05
------=_Part_92922_30569948.1162055804001
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I wrote five because I started to count 5 times ago. My RAM is in good
condition :) Problem with reiserfs (reiser4 is used across the net to
specify version 4.X IMHO) occurs on many machines - servers, backup servers
(rsync once a day), desktop computers (3 or 4), laptop (only one).
Every one of them was tested and works with ext3 (but it has limit of
subdirs), every one of them works fine under UFS2 (freebsd, limit of dirs,
too). Some of those servers work hard with mysql,php,apache (more than 2000
queries per second) and errors occurs randomly... 1 per week.
Backup servers doesn't do very much - only one rsync process at a time and
this is enough to break reiserfs.
To resume:
1. reiserfs breaks down on power failures even with option data=journal or
sync
2. reiserfs breaks down on every machine that I have - from pentium-mmx to
Core2Duo, about 10 machines
3. reiserfs breaks down on heavy load (/proc/loadavg=35), and low load(=0.1),
*it only takes a time*
4. reiserfs broke down on all partitions that was using reiserfs
5. reiserfs breaks down on 2.4.21+ and some older
6. reiserfs breaks down on 2.6.17, ..18 and older that I can't remember
7. ram, disks, cables was tested, changed, and problem stays
8. ...sata, ata/pata
9. maybe those are just accidents but they occur too often to call them just
accidents
Conclusions:
1. UPS will not help you with reiserfs
2. Do not use reiserfs on production systems
3. "quite stable" means "works for them, not for me".
4. journal only slows things down and does not preserve any consistency
My questions:
1. Is there the file system that preserves data & metadata like UFS2 ????
"solid as rock!"
2. What options do I need to enable (mount/mkfs) for XFS or JFS to enable
FULL journaling?
3. How to bypass limit od 32000 dirs on ext3?
4. Is there an option in kernel and how to enable it to sync on Oops and
reboot?
On 10/28/06, Norberto Bensa <nbensa@gmx.net> wrote:
>
> CapSel wrote:
> > So my question is - how can I help to eliminate this bug(s)?
>
> Can you check your RAM please? Reiserfs (3.x that is) is very stable. I'm
> using it for five years now. No data loss or corruption.
>
> And DON'T use XFS if you can't afford an UPS.
>
>
> Regards,
> Norberto
>
>
>
------=_Part_92922_30569948.1162055804001
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I wrote five because I started to count 5 times ago. My RAM is in good condition :) Problem with reiserfs (reiser4 is used across the net to specify version 4.X IMHO) occurs on many machines - servers, backup servers (rsync once a day), desktop computers (3 or 4), laptop (only one).
<br> Every one of them was tested and works with ext3 (but it has limit of subdirs), every one of them works fine under UFS2 (freebsd, limit of dirs, too). Some of those servers work hard with mysql,php,apache (more than 2000 queries per second) and errors occurs randomly... 1 per week.
<br> Backup servers doesn't do very much - only one rsync process at a time and this is enough to break reiserfs.<br><br>To resume:<br>1. reiserfs breaks down on power failures even with option data=journal or sync<br>2. reiserfs breaks down on every machine that I have - from pentium-mmx to Core2Duo, about 10 machines
<br>3. reiserfs breaks down on heavy load (/proc/loadavg=35), and low load(=0.1), *it only takes a time*<br>4. reiserfs broke down on all partitions that was using reiserfs<br>5. reiserfs breaks down on 2.4.21+ and some older
<br>6. reiserfs breaks down on 2.6.17, ..18 and older that I can't remember<br>7. ram, disks, cables was tested, changed, and problem stays<br>8. ...sata, ata/pata<br>9. maybe those are just accidents but they occur too often to call them just accidents
<br><br>Conclusions:<br>1. UPS will not help you with reiserfs<br>2. Do not use reiserfs on production systems<br>3. "quite stable" means "works for them, not for me".<br>4. journal only slows things down and does not preserve any consistency
<br><br>My questions:<br>1. Is there the file system that preserves data & metadata like UFS2 ???? "solid as rock!"<br>2. What options do I need to enable (mount/mkfs) for XFS or JFS to enable FULL journaling?
<br>3. How to bypass limit od 32000 dirs on ext3?<br>4. Is there an option in kernel and how to enable it to sync on Oops and reboot?<br><br><div><span class="gmail_quote">On 10/28/06, <b class="gmail_sendername">Norberto Bensa
</b> <<a href="mailto:nbensa@gmx.net">nbensa@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">CapSel wrote:<br>
> So my question is - how can I help to eliminate this bug(s)?<br><br>Can you check your RAM please? Reiserfs (3.x that is) is very stable. I'm<br>using it for five years now. No data loss or corruption.<br><br>And DON'T use XFS if you can't afford an UPS.
<br><br><br>Regards,<br>Norberto<br><br><br></blockquote></div><br>
------=_Part_92922_30569948.1162055804001--
--
gentoo-user@gentoo.org mailing list