[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201004201926.33908.bernd.schubert@fastmail.fm>
Date: Tue, 20 Apr 2010 19:26:33 +0200
From: Bernd Schubert <bernd.schubert@...tmail.fm>
To: Eric Sandeen <sandeen@...hat.com>
Cc: Andre Noll <maan@...temlinux.org>,
Andrew Vasquez <andrew.vasquez@...gic.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
Linux Driver <Linux-Driver@...gic.com>,
Thomas Helle <Helle@...bingen.mpg.de>
Subject: Re: ext4: (2.6.34-rc4): This should not happen!! Data will be lost
On Tuesday 20 April 2010, Eric Sandeen wrote:
> On 04/20/2010 10:37 AM, Andre Noll wrote:
> ...
>
> > - device timeout 30s, nobarrier
> > No problem at all, all three runs OK.
> >
> > Eric, are you still interested in seeing the blktrace output? Suppose,
> > I should use a 30s timeout, nodealloc and barriers=1 as this triggers
> > the problem within minutes.
>
> Hm, so something about barriers being issued is causing timeout
> problems on the device...?
I think interesting at this point would be the exact model of the Infortrend
device. There are some completely broken models (IMHO), which have two
controllers for redundancy. 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. More recent IFT dual-controller units do not suffer from this bug
anymore, but as Andre said, they are using an old unit...
Thanks,
Bernd
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists