From: Brian Jackson <notiggy@gmail.com>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: external drive size differences
Date: Tue, 17 Aug 2004 13:37:11 -0500 [thread overview]
Message-ID: <fb20c214040817113715e6202b@mail.gmail.com> (raw)
In-Reply-To: <20040815093759.GK31901@lbsd.net>
On Sun, 15 Aug 2004 11:37:59 +0200, Nigel Kukard <nkukard@lbsd.net> wrote:
> Something very very interesting... below is an external drive enclosure
> supporting both USB2 and Firwire, fitted with a 200Gb IDE Hdd.
>
> When plugged into the firewire bus, i get 137Gb size, when plugged into
> the usb bus, i get 200Gb size.
>
> Could this be a bug in the kernel? or external hardware?
More than likely hardware. Most of the oxford chips that are so often
used in firewire enclosures, don't support >137G drives. It probably
uses a different chip for the usb side of things.
--Iggy
>
> <snip>
> ieee1394: sbp2: Logged into SBP-2 device
> ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
> Vendor: WDC WD20 Model: 00JB-00FUA0 Rev:
> Type: Direct-Access ANSI SCSI revision: 06
> SCSI device sdb: 268435455 512-byte hdwr sectors (137439 MB)
> sdb: asking for cache data failed
> sdb: assuming drive cache: write through
> sdb: sdb1
> </snip>
>
> <snip>
> scsi7 : SCSI emulation for USB Mass Storage devices
> Vendor: USB 2.0 Model: Storage Device Rev: 0100
> Type: Direct-Access ANSI SCSI revision: 02
> SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
> sdb: assuming drive cache: write through
> sdb: sdb1
> </snip>
>
> Regards
> Nigel Kukard
prev parent reply other threads:[~2004-08-17 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 9:37 external drive size differences Nigel Kukard
2004-08-15 11:59 ` Alan Cox
2004-08-15 14:07 ` Nigel Kukard
2004-08-15 13:07 ` Alan Cox
2004-08-15 14:26 ` Nigel Kukard
2004-08-17 18:37 ` Brian Jackson [this message]
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=fb20c214040817113715e6202b@mail.gmail.com \
--to=notiggy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nkukard@lbsd.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.