Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751967AbYJ0Pdc (ORCPT ); Mon, 27 Oct 2008 11:33:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751407AbYJ0PdS (ORCPT ); Mon, 27 Oct 2008 11:33:18 -0400 Received: from accolon.hansenpartnership.com ([76.243.235.52]:49625 "EHLO accolon.hansenpartnership.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751768AbYJ0PdR (ORCPT ); Mon, 27 Oct 2008 11:33:17 -0400 Subject: Re: usb hdd problems with 2.6.27.2 From: James Bottomley To: Alan Stern Cc: Douglas Gilbert , Luciano Rocha , "Rafael J. Wysocki" , Linux-Kernel , USB list , SCSI development list In-Reply-To: References: Content-Type: text/plain Date: Mon, 27 Oct 2008 10:33:12 -0500 Message-Id: <1225121592.5146.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 (2.22.3.1-1.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 24 On Mon, 2008-10-27 at 11:25 -0400, Alan Stern wrote: > On Mon, 27 Oct 2008, Douglas Gilbert wrote: > > BTW a single disk in RAID 0 (seen on a HP E200 controller) > > has a shortened capacity value seen in the midlevel on the > > corresponding logical drive. That missing chunk is probably > > where the RAID controller puts its control information. > > Anyway, playing with the capacity value returned by READ > > CAPACITY certainly has a precedent. > > usb-storage isn't in the business of altering the data it gets from a > device. It's just a transport. That's why the sdev->fix_capacity flag > exists; we tell the upper layer that the data it gets is going to be > wrong and let the upper layer worry about fixing things up. And you do this by setting US_FL_FIX_CAPACITY in unusual_devs.h James -- 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/