linux-ext4 - Re: Weird I/O errors with USB hard drive not remounting filesystem readonly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0911231004030.2958-100000@iolanthe.rowland.org>
Date:	Mon, 23 Nov 2009 10:06:03 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Jan Kara <jack@...e.cz>
cc:	tmhikaru@...il.com, <linux-kernel@...r.kernel.org>,
	<linux-usb@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
	<linux-scsi@...r.kernel.org>, <linux-ext4@...r.kernel.org>
Subject: Re: Weird I/O errors with USB hard drive not remounting filesystem
 readonly

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

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html