From: Jan Kara <jack@suse.cz>
To: tmhikaru@gmail.com
Cc: Jan Kara <jack@suse.cz>,
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 11:54:40 +0100 [thread overview]
Message-ID: <20091123105440.GB15679@duck.suse.cz> (raw)
In-Reply-To: <20091123080919.GA3115@roll>
Hi,
On Mon 23-11-09 03:09:19, tmhikaru@gmail.com wrote:
> Okay, finally had some time to dismantle the machine in question and
> inserted the backup drive without the enclosure. Now that I was able to get
> smartctl to give me information on what was going on, it seems there's
> nothing wrong with the drive itself (no remapped sectors, nothing prefail or
> fail going wrong, drive's smart status is good) but it's had a history of
> 406 (!!!) errors reported, the last five happening within the same second,
> all of which seem (to my untrained eye) to imply a bad IDE cable. Which
> means likely my USB enclosure is screwing up.
>
> To be sure, I did some extended testing with it hooked up: Tried
> doing a full and incremental backup of my machine with no errors reported,
> as well as an offline and then immediately afterwards, long test via
> smartctl. Nothing changed in the output.
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.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2009-11-23 10: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 [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:54 ` Jan Kara
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=20091123105440.GB15679@duck.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=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).