From: Jan Kara <jack@suse.cz>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jan Kara <jack@suse.cz>,
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 19:54:50 +0100 [thread overview]
Message-ID: <20091123185449.GA11186@quack.suse.cz> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911231319060.2958-100000@iolanthe.rowland.org>
On Mon 23-11-09 13:20:26, Alan Stern wrote:
> On Mon, 23 Nov 2009, Jan Kara wrote:
>
> > On Mon 23-11-09 10:06:03, Alan Stern wrote:
> > > 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.
> > Well, if you could provide me with the patch, I could try to track down
> > why the errors aren't propagated... It would be interesting because if it's
> > not some retry logic in block layer, it's a bug in VFS ;).
>
> I can't provide a patch without first knowing what the errors are. The
> way to find out is to use usbmon. See Documentation/usb/usbmon.txt for
> instructions.
Ah, OK. The problem manifests itself as an error in SATA communication
(which in fact somehow happens over USB, but I don't really know the
details of mass storage over USB) so debugging USB would become actual only
if we found out it's really some bug in an usb stack. But so far the most
probable is just an error somewhere between the USB controller in the
enclosure and the drive itself. BTW: Is the data transferred over USB
checksummed?
Honza
next prev parent reply other threads:[~2009-11-23 18:54 UTC|newest]
Thread overview: 28+ 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 16:09 ` Jan Kara
2009-11-23 18:20 ` Alan Stern
2009-11-23 18:54 ` Jan Kara [this message]
2009-11-23 19:50 ` tmhikaru
2009-11-23 20:06 ` tmhikaru-Re5JQEeQqe8AvxtiuMwx3w
2009-11-23 20:33 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0911231533071.2958-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2009-11-23 23:42 ` tmhikaru-Re5JQEeQqe8AvxtiuMwx3w
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:56 ` Jan Kara
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-27 9:43 ` tmhikaru
2009-11-27 13:13 ` Jan Kara
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=20091123185449.GA11186@quack.suse.cz \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--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=stern@rowland.harvard.edu \
--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 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).