All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Vasquez <andrew.vasquez@qlogic.com>
To: Andre Noll <maan@systemlinux.org>
Cc: 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: Fri, 16 Apr 2010 09:36:54 -0700	[thread overview]
Message-ID: <20100416163654.GD58339@plapa.qlogic.org> (raw)
In-Reply-To: <20100416160856.GA25507@skl-net.de>

On Fri, 16 Apr 2010, Andre Noll wrote:

> On 08:52, Andrew Vasquez wrote:
> > The driver here is simply reporting that the a command's timeout value
> > had been exceeded and the mid-layer began error-recovery with a request
> > to 'abort' the command.  The abort-request completed successfully:
> > 
> > 	qla2xxx 0000:06:09.0: scsi(0:0:0): Abort command issued -- 1 fa6a73 2002.
> > 
> > I can't explain why the storage did not complete the request in the
> > allotted time.
> 
> Ah, that's valuable information, thanks. The underlying Infortrend
> Raid System is rather old but worked without any problems for several
> years. We recently replaced its 400G disks by new 2T WD disks. Maybe
> the new disks have longer response times, could that be the reason? And
> is there a way to increase the timeout value?

To update the default timeout value (30 seconds) for commands
submitted to /dev/sdn to 60 seconds:

        $ echo 60 > /sys/block/sdn/device/timeout

-- av

  reply	other threads:[~2010-04-16 16:42 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 [this message]
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
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=20100416163654.GD58339@plapa.qlogic.org \
    --to=andrew.vasquez@qlogic.com \
    --cc=Helle@tuebingen.mpg.de \
    --cc=Linux-Driver@qlogic.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=maan@systemlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.