From: Andre Noll <maan@systemlinux.org>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Eric Sandeen <sandeen@redhat.com>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Linux Driver <Linux-Driver@qlogic.com>,
Thomas Helle <Helle@tuebingen.mpg.de>
Subject: Re: ext4: (2.6.34-rc4): This should not happen!! Data will be lost
Date: Tue, 20 Apr 2010 20:35:33 +0200 [thread overview]
Message-ID: <20100420183533.GA21495@skl-net.de> (raw)
In-Reply-To: <201004201926.33908.bernd.schubert@fastmail.fm>
[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]
On 19:26, Bernd Schubert wrote:
> On Tuesday 20 April 2010, Eric Sandeen wrote:
> I think interesting at this point would be the exact model of the Infortrend
> device.
Here's the system information as reported by the telnet interface:
CPU Type PPC750FX
Total Cache Size 2048MB DDR(ECC)
Firmware Version 3.42I.03
Bootrecord Version 1.23A
FW Upgradability Rev. C
Serial Number 6912121
Battery Backup Unit Present
Base Board Rev. ID 0
Base Board ID 81
ID of NVRAM Defaults A16F-G2221 V6.10
Controller Position Slot A
> There are some completely broken models (IMHO), which have two
> controllers for redundancy.
This is a 4 year old system (which does not support Raid6). It has only
a single controller though.
> Now with enabled write-back cache, it can happen that those units run
> into some kind of firmware bug. It then takes about 2h to flush 2GB of
> write-back cache. The telnet interface will show the status of the
> cache.
Hey, I saw this once on a different (newer) infortrend system. However,
it might still be hapening on this system as well and cause the timeout
problems.
Guess I'll have to check if there's a more recent firmware for this
system..
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-04-20 18:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 12:35 ext4: (2.6.34-rc4): This should not happen!! Data will be lost Andre Noll
2010-04-16 14:29 ` tytso
2010-04-16 15:02 ` Eric Sandeen
2010-04-16 15:30 ` Andre Noll
2010-04-16 15:43 ` Eric Sandeen
2010-04-16 15:52 ` Andrew Vasquez
2010-04-16 16:08 ` Andre Noll
2010-04-16 16:36 ` Andrew Vasquez
2010-04-16 17:07 ` Andre Noll
2010-04-17 16:55 ` Bernd Schubert
2010-04-17 18:19 ` Andre Noll
2010-04-17 18:43 ` Bernd Schubert
2010-04-17 20:45 ` Eric Sandeen
2010-04-17 22:38 ` Andre Noll
2010-04-20 15:37 ` Andre Noll
2010-04-20 16:51 ` Eric Sandeen
2010-04-20 17:26 ` Bernd Schubert
2010-04-20 18:35 ` Andre Noll [this message]
2010-04-20 20:09 ` Bernd Schubert
2010-04-20 17:46 ` Andre Noll
2010-04-22 8:21 ` Andre Noll
2010-04-21 8:57 ` Dmitry Monakhov
2010-04-21 13:47 ` Andre Noll
2010-04-16 15:57 ` Andre Noll
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=20100420183533.GA21495@skl-net.de \
--to=maan@systemlinux.org \
--cc=Helle@tuebingen.mpg.de \
--cc=Linux-Driver@qlogic.com \
--cc=andrew.vasquez@qlogic.com \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).