From: Alan Stern <stern@rowland.harvard.edu>
To: Jan Kara <jack@suse.cz>
Cc: tmhikaru@gmail.com, <linux-kernel@vger.kernel.org>,
<linux-usb@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
<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: Mon, 23 Nov 2009 10:06:03 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0911231004030.2958-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20091123105440.GB15679@duck.suse.cz>
On Mon, 23 Nov 2009, Jan Kara wrote:
> Yeah, from what you write, it looks like USB enclosure is at fault (or it
> could still be your USB controller but I doubt it). It's still a bit
> bothering that the error reported by the drive was not properly propagated
> up to VFS. Either it's some block layer retry/ignore magic that I missed or
> we ignore errors from block layer in some place.
Is there any interest in tracking this down? It's not hard to find out
what low-level errors are being reported and to generate them on demand
with an emulated USB disk drive.
Alan Stern
WARNING: multiple messages have this Message-ID (diff)
From: Alan Stern <stern@rowland.harvard.edu>
To: Jan Kara <jack@suse.cz>
Cc: tmhikaru@gmail.com, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
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: Mon, 23 Nov 2009 10:06:03 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0911231004030.2958-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <20091123105440.GB15679@duck.suse.cz>
On Mon, 23 Nov 2009, Jan Kara wrote:
> Yeah, from what you write, it looks like USB enclosure is at fault (or it
> could still be your USB controller but I doubt it). It's still a bit
> bothering that the error reported by the drive was not properly propagated
> up to VFS. Either it's some block layer retry/ignore magic that I missed or
> we ignore errors from block layer in some place.
Is there any interest in tracking this down? It's not hard to find out
what low-level errors are being reported and to generate them on demand
with an emulated USB disk drive.
Alan Stern
next prev parent reply other threads:[~2009-11-23 15:05 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 [this message]
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
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.0911231004030.2958-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=axboe@kernel.dk \
--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.