mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manfred Wassmann <tux.wassmann@googlemail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: contact problem? (was Re: Spurious Filesystem corruption with ext3 +  large (<400GB) hw RAID ...)
Date: Fri, 13 Feb 2009 17:29:36 +0100	[thread overview]
Message-ID: <6bd94bae0902130829r15e6eacag25220487457027ad@mail.gmail.com> (raw)

On Fri, Feb 6, 2009 at 7:50 PM, Ray Lee <ray-lk@madrabbit.org> wrote:

> Huh. It may be related to whatever kernel version Ubuntu uses to boot
> up the install media. Try a different version of Ubuntu (older, newer
> if a newer one exists) to see if it has the same problem.

Thank you for your notice but as I mentioned the problem occurred
first with my custom built kernel and the Ubuntu installation disk was
used only to reproduce the error -- Ubuntu is not what I use anyhow,
I'm on Debian since I switched from Slackware in 1995 ;-)

But now it looks like we had an exotic hardware problem here. Just
before the weekend the RAID controller reported a degraded array and
switched to the hotspare disk. On Monday the original array was
recreated and everything worked fine until Tuesday morning when the
array again was degraded. But then since the disk was checked and
reinserted into the array all problems are gone :-\

Is it possible that such a problem is caused by bad contact within the
drive bay connector?

The reason why it occurred with ext3 only might then be that ext3
stores it's backup superblocks at addresses which are otherwise unused
by a largely empty filesystem.

regards Manfred
-- 
Unix "Birthday" on 2009-02-13 23:31:30 UTC
...it's 1234567890 seconds since the epoch.

             reply	other threads:[~2009-02-13 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 16:29 Manfred Wassmann [this message]
2009-02-14 17:40 ` Ray Lee
2009-02-28 19:32   ` 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=6bd94bae0902130829r15e6eacag25220487457027ad@mail.gmail.com \
    --to=tux.wassmann@googlemail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®