Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755506AbZKWQJM (ORCPT ); Mon, 23 Nov 2009 11:09:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754871AbZKWQJL (ORCPT ); Mon, 23 Nov 2009 11:09:11 -0500 Received: from cantor.suse.de ([195.135.220.2]:43233 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754684AbZKWQJK (ORCPT ); Mon, 23 Nov 2009 11:09:10 -0500 Date: Mon, 23 Nov 2009 17:09:14 +0100 From: Jan Kara To: Alan Stern Cc: Jan Kara , tmhikaru@gmail.com, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, Jens Axboe , linux-scsi@vger.kernel.org, linux-ext4@vger.kernel.org Subject: Re: Weird I/O errors with USB hard drive not remounting filesystem readonly Message-ID: <20091123160914.GG15679@duck.suse.cz> References: <20091123105440.GB15679@duck.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1149 Lines: 25 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 ;). Honza -- Jan Kara SUSE Labs, CR -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/