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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
