mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Manfred Wassmann <tux.wassmann@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Spurious Filesystem corruption with ext3 + large (<400GB) hw RAID partition + SMP
Date: Sat, 31 Jan 2009 11:46:51 -0200	[thread overview]
Message-ID: <20090131134651.GC28763@khazad-dum.debian.net> (raw)
In-Reply-To: <6bd94bae0901310536l2cd42fa1off60ee066fa0096b@mail.gmail.com>

On Sat, 31 Jan 2009, Manfred Wassmann wrote:
> I'm experiencing spurious filesystem corruption problems with ext3 on
> a partition larger than 400 GB on a hardware SATA RAID.

Please describe the SATA RAID hardware in a bit more detail.  Which
SATA controller does it use?

Also, have you made sure it is not caused by bad memory?

> The problems first occured on an Intel dual core system with a custom
> installation DVD which uses a 32 bit 2.6.26 kernel with SMP enabled
> and a 4GB memory limit. The problems occured only randomly but it was
> possible to reproduce them reliably with a standard Ubunu installation
> disk using a 2.6.27-7 kernel (apparently also 32bit SMP kernel w 4GB
> limit).
> When installing Ubuntu a message appears in the kernel log stating:
> "EXT3-fs error (device sda6): ext3_vlid_block_bitmap: Invalid block
> bitmap - block_group = 3076, block = <some large number>"
> This message is the first indication of any problem, the filesystem is
> then remounted readonly and the installation stops understandably.
> 
> The problem does only occur with an ext3 filesystem, installation
> using an xfs filesystem completes without error.
> 
> Furthermore with the installation from my custom installation DVD
> succeeded, which installs a prebuild Debian etch system featuring a 64
> bit monolithic 2.6.26 kernel, i was able to stress the system to its
> limits using the stress and dbench programs without any sign of
> filesystem corruption.
> 
> As XFS does substantially outperform ext3 under the given
> circumstances I'm going to use that but if someone wants to
> investigate the problem and needs further details I'll do my very best
> ;-)

Be careful.  XFS might not trigger the problem as readly, but it could
still be there and you can suffer data loss.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  reply	other threads:[~2009-01-31 13:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-31 13:36 Manfred Wassmann
2009-01-31 13:46 ` Henrique de Moraes Holschuh [this message]
     [not found]   ` <6bd94bae0901310604u6ed876f1n77b7e2561f479ad1@mail.gmail.com>
2009-01-31 14:51     ` Manfred Wassmann
2009-02-01  1:44       ` Henrique de Moraes Holschuh
2009-02-06 18:08         ` Manfred Wassmann
2009-02-06 18:50           ` Ray Lee
2009-02-14 13:57             ` Manfred Wassmann
     [not found]     ` <1233415163.28790.1297773583@webmail.messagingengine.com>
2009-01-31 17:26       ` Manfred Wassmann

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=20090131134651.GC28763@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tux.wassmann@googlemail.com \
    /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

all inboxes | Powered by JetHome®