[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <6bd94bae0902130829r15e6eacag25220487457027ad@mail.gmail.com>
Date: Fri, 13 Feb 2009 17:29:36 +0100
From: Manfred Wassmann <tux.wassmann@...glemail.com>
To: linux-kernel <linux-kernel@...r.kernel.org>
Subject: contact problem? (was Re: Spurious Filesystem corruption with ext3 +
large (<400GB) hw RAID ...)
On Fri, Feb 6, 2009 at 7:50 PM, Ray Lee <ray-lk@...rabbit.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists