linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Noll <maan@systemlinux.org>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Eric Sandeen <sandeen@redhat.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: Sat, 17 Apr 2010 20:19:12 +0200	[thread overview]
Message-ID: <20100417181912.GC25507@skl-net.de> (raw)
In-Reply-To: <201004171855.36874.bernd.schubert@fastmail.fm>

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

On 18:55, Bernd Schubert wrote:
> > > To update the default timeout value (30 seconds) for commands
> > > submitted to /dev/sdn to 60 seconds:
> > >
> > >         $ echo 60 > /sys/block/sdn/device/timeout
> > 
> > I will re-run the stress test with a 60 seconds timeout value and follow
> > up if this did not help.
> 
> That will not help if the command is "SYNCHRONIZE_CACHE", as that ignores 
> device settings, but uses scsi default timeout (30s), which is far too small 
> for SATA based raid units. Scsi maintainers ignored that and a couple of other 
> patches I wrote to improve error handling with Infortrend units. Will send the 
> patches again soon.

Please CC me when you do so. The machine I am having trouble with is
only our fallback server. I can use it freely for testing and am willing
to give your patches a try.

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 --]

  reply	other threads:[~2010-04-17 18:19 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 [this message]
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
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=20100417181912.GC25507@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).