On Wed, 27 Aug 2014, Oliver Neukum wrote:
> > I don't think we want to add another SCSI flag to say that READ
> > CAPACITY(10) is unreliable.
>
> Why not? It would only be friendly to tell the upper layer
> of a malfunction if we know about it.
To what end? What will the upper layer do with thi
On Tue, 2014-08-26 at 10:47 -0400, Alan Stern wrote:
> On Mon, 25 Aug 2014, Oliver Neukum wrote:
> > Just set US_FL_NEEDS_CAP16. If READ CAPACITY(16) fails in that case,
> > it is clear that something is wrong. It must be set or READ CAPACITY(10)
> > alone would be taken as giving a valid answer.
On Mon, 25 Aug 2014, Oliver Neukum wrote:
> On Mon, 2014-08-25 at 16:21 -0400, Alan Stern wrote:
> > On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
> >
> > > Well, it is causing problems anyway... from user perspective, it's a
> > > Linux compatibility issue, as it works "fine" on Windows. I'
On Mon, 26 Aug 2014, David Leight wrote:
> I wonder what the manufacturer would saw in response the bug where
> windows shows the incorrect size when trying to partition the disk?
I contacted enclosure manufacturer (Welland) some weeks ago, they are supposed
to escalate my questions to enginee
From Oliver Neukum [mailto:oneu...@suse.de]
> On Tue, 2014-08-26 at 09:58 +, David Laight wrote:
> > > Part of the problem is that usb-storage has no way to know that
> > > anything strange is going on. It's normal for READ CAPACITY(16) to
> > > fail (this depend on the SCSI level), and it's n
On Tue, 2014-08-26 at 09:58 +, David Laight wrote:
> > Part of the problem is that usb-storage has no way to know that
> > anything strange is going on. It's normal for READ CAPACITY(16) to
> > fail (this depend on the SCSI level), and it's normal for the READ
> > CAPACITY(10) to report a valu
From: Alan Stern
> On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
>
> > Well, it is causing problems anyway... from user perspective, it's a
> > Linux compatibility issue, as it works "fine" on Windows. I'm not an
> > expert, but I'm wondering that if usb-storage could set capacity as
> > "UND
On Mon, 2014-08-25 at 16:21 -0400, Alan Stern wrote:
> On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
>
> > Well, it is causing problems anyway... from user perspective, it's a
> > Linux compatibility issue, as it works "fine" on Windows. I'm not an
> > expert, but I'm wondering that if usb-st
On Mon, 25 Aug 2014 Alan Stern wrote:
> Part of the problem is that usb-storage has no way to know that anything
> strange is going on. It's normal for READ CAPACITY(16) to fail (this depend
> on
> the SCSI level), and it's normal for the READ
> CAPACITY(10) to report a value less than 2 TB.
> R
On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
> Well, it is causing problems anyway... from user perspective, it's a
> Linux compatibility issue, as it works "fine" on Windows. I'm not an
> expert, but I'm wondering that if usb-storage could set capacity as
> "UNDETERMINED"/ Zero (or keep usi
On Mon, 25 Aug 2014 Alan Stern wrote:
>
> On Mon, 25 Aug 2014, Alfredo Dal Ava Junior wrote:
>
> That's right. I don't know why Windows behaves that way.
Please look this output from diskpart (Windows):
DISKPART> list partition
Partition ### Type Size Offset
---
On Mon, 15 Aug 2014 James Bottomley wrote:
> So how did the partition get on there at the correct size in the first place?
> Even under windows partition managers believe the disk size they get from
> the system if the disk is blank.
The HDD can be partitioned outside the enclosure, when connect
12 matches
Mail list logo
