All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Jan Kara <jack@suse.cz>
Cc: Boaz Harrosh <bharrosh@panasas.com>, <tmhikaru@gmail.com>,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	<linux-ext4@vger.kernel.org>
Subject: Re: Weird I/O errors with USB hard drive not remounting filesystem readonly
Date: Tue, 24 Nov 2009 15:13:01 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0911241510590.2881-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20091124195607.GC16662@quack.suse.cz>

On Tue, 24 Nov 2009, Jan Kara wrote:

>   After digging in block layer code, it's as we suspected:
> In case of host error DID_ERROR (which is our case), scsi request is
> retried iff it is not a FAILFAST request which is set if bio is doing
> readahead... So this is explained and everything behaves as it should.
> Thanks everybody involved :).

Okay, very good.  There remains the question of the disturbing error
messages in the system log.  Should they be supressed for FAILFAST
requests?

Alan Stern


WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu>
To: Jan Kara <jack@suse.cz>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
	tmhikaru@gmail.com,
	Kernel development list <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>,
	SCSI development list <linux-scsi@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: Weird I/O errors with USB hard drive not remounting filesystem readonly
Date: Tue, 24 Nov 2009 15:13:01 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.0911241510590.2881-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20091124195607.GC16662@quack.suse.cz>

On Tue, 24 Nov 2009, Jan Kara wrote:

>   After digging in block layer code, it's as we suspected:
> In case of host error DID_ERROR (which is our case), scsi request is
> retried iff it is not a FAILFAST request which is set if bio is doing
> readahead... So this is explained and everything behaves as it should.
> Thanks everybody involved :).

Okay, very good.  There remains the question of the disturbing error
messages in the system log.  Should they be supressed for FAILFAST
requests?

Alan Stern


  reply	other threads:[~2009-11-24 20:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-13  5:09 Weird I/O errors with USB hard drive not remounting filesystem readonly tmhikaru
2009-11-19 16:07 ` Jan Kara
     [not found]   ` <20091120082359.GA29538@roll>
     [not found]     ` <20091120094641.GB15422@duck.suse.cz>
2009-11-23  8:09       ` tmhikaru
2009-11-23 10:54         ` Jan Kara
2009-11-23 15:06           ` Alan Stern
2009-11-23 15:06             ` Alan Stern
2009-11-23 16:09             ` Jan Kara
2009-11-23 18:20               ` Alan Stern
2009-11-23 18:20                 ` Alan Stern
2009-11-23 18:54                 ` Jan Kara
2009-11-23 19:50                   ` tmhikaru
2009-11-23 20:06                     ` tmhikaru
2009-11-23 20:06                       ` tmhikaru-Re5JQEeQqe8AvxtiuMwx3w
2009-11-23 20:33                       ` Alan Stern
2009-11-23 20:33                         ` Alan Stern
2009-11-23 23:42                         ` tmhikaru
2009-11-23 23:42                           ` tmhikaru-Re5JQEeQqe8AvxtiuMwx3w
2009-11-24 17:16                           ` Alan Stern
2009-11-24 17:16                             ` Alan Stern
2009-11-24 17:47                             ` Boaz Harrosh
2009-11-24 19:28                               ` Alan Stern
2009-11-24 19:28                                 ` Alan Stern
2009-11-24 19:56                                 ` Jan Kara
2009-11-24 20:13                                   ` Alan Stern [this message]
2009-11-24 20:13                                     ` Alan Stern
2009-11-24 20:39                                     ` Jan Kara
2009-11-24 21:50                                       ` tmhikaru
2009-11-24 22:23                                         ` tmhikaru
2009-11-25  8:42                                           ` Jan Kara
2009-11-25  9:37                                             ` tmhikaru
2009-11-25 16:10                                             ` Alan Stern
2009-11-25 16:10                                               ` Alan Stern
2009-11-27  9:43                                               ` tmhikaru
2009-11-27 13:13                                                 ` Jan Kara
2009-11-27 17:58                                                 ` Alan Stern
2009-11-27 17:58                                                   ` Alan Stern
2009-11-27 17:58                                                   ` Alan Stern
2009-11-29  4:30                                                   ` tmhikaru
2009-11-24 18:00                             ` Jan Kara

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=Pine.LNX.4.44L0.0911241510590.2881-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=axboe@kernel.dk \
    --cc=bharrosh@panasas.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tmhikaru@gmail.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.