From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Douglas Gilbert <dgilbert@interlog.com>,
Luciano Rocha <luciano@eurotux.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: usb hdd problems with 2.6.27.2
Date: Mon, 27 Oct 2008 10:33:12 -0500 [thread overview]
Message-ID: <1225121592.5146.9.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0810271117530.4059-100000@iolanthe.rowland.org>
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
next prev parent reply other threads:[~2008-10-27 15:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081022162246.GB5649@bit.office.eurotux.com>
2008-10-25 19:25 ` usb hdd problems with 2.6.27.2 Rafael J. Wysocki
[not found] ` <200810252125.44184.rjw-KKrjLPT3xs0@public.gmane.org>
2008-10-25 19:50 ` Alan Stern
2008-10-25 20:11 ` James Bottomley
2008-10-26 14:05 ` Luciano Rocha
2008-10-27 11:14 ` Luciano Rocha
2008-10-27 11:28 ` Luciano Rocha
[not found] ` <20081027112803.GA4398-oEplIgxCSygGFt9iVWuREaMaJEuR8uiQ@public.gmane.org>
2008-10-27 14:24 ` Alan Stern
2008-10-27 14:56 ` Douglas Gilbert
[not found] ` <4905D68D.7030407-qazKcTl6WRFWk0Htik3J/w@public.gmane.org>
2008-10-27 15:08 ` Boaz Harrosh
[not found] ` <4905D986.6050001-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2008-10-27 16:26 ` Kay Sievers
2008-10-27 15:25 ` Alan Stern
2008-10-27 15:33 ` James Bottomley [this message]
2008-10-27 15:18 ` Luciano Rocha
2008-10-27 15:38 ` Alan Stern
[not found] ` <Pine.LNX.4.44L0.0810271134530.15462-100000-IYeN2dnnYyZXsRXLowluHWD2FQJk+8+b@public.gmane.org>
2008-10-27 16:53 ` Luciano Rocha
[not found] ` <20081027165306.GA3875-oEplIgxCSygGFt9iVWuREaMaJEuR8uiQ@public.gmane.org>
2008-10-27 20:10 ` Alan Stern
2008-10-28 16:37 ` Luciano Rocha
[not found] ` <20081028163722.GA4374-oEplIgxCSygGFt9iVWuREaMaJEuR8uiQ@public.gmane.org>
2008-10-28 17:38 ` Alan Stern
2008-11-03 15:52 ` Luciano Rocha
[not found] ` <20081103155254.GA3368-oEplIgxCSygGFt9iVWuREaMaJEuR8uiQ@public.gmane.org>
2008-11-03 19:46 ` Alan Stern
2008-11-05 10:26 ` Luciano Rocha
2008-11-05 16:51 ` Alan Stern
2008-11-13 17:10 ` Luciano Rocha
2008-10-27 20:36 ` Alan Stern
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=1225121592.5146.9.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=dgilbert@interlog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luciano@eurotux.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
/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