From: Simon Burley <simonb@lipsyncpost.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: didier@ece.gatech.edu, "'Justin T. Gibbs'" <gibbs@scsiguy.com>,
linux-scsi@vger.kernel.org
Subject: Re: Pb between an UltraTrak SX8000 and an Adaptec 29160
Date: Wed, 20 Nov 2002 15:22:16 +0000 [thread overview]
Message-ID: <3DDBA8A8.F370532E@lipsyncpost.co.uk> (raw)
In-Reply-To: 1037626683.7486.10.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
<snip>
> Linux 2.4.x doesnt support single volumes over 1Tb. Thats fixed in 2.5
Can I ask what the symptoms of this failure to support >1Tb volumes
would be? Failure to identify the device? Random read/write failures?
Completely corrupted disk? It's the first time I've heard this!
The reason I ask is because we have a Storcase IDE to SCSI raid
enclosure with RAID controller here containing 8x Maxtor 160Gb disks
(configured as one RAID 3 volume), and it has been 100% reliable since
day one. No strangeness, failures of any sort, errors in syslog etc.
Vendor: DS570 Model: Rev: 0001
Type: Direct-Access ANSI SCSI revision: 03
scsi2:A:6:0: Tagged Queuing enabled. Depth 253
(scsi2:A:6): 160.000MB/s transfers (80.000MHz DT, offset 31, 16bit)
SCSI device sdb: -2053816320 512-byte hdwr sectors (47958 MB)
So I see the same problem as Didier, but fdisk version 2.11f got the
size right under 2.4.19-ac4:
df -kl
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/sdb1 1102989912 847397312 199563908 81% /local
Or am I missing something?
Simon
next prev parent reply other threads:[~2002-11-20 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 20:50 Pb between an UltraTrak SX8000 and an Adaptec 29160 didier
2002-11-15 19:53 ` Justin T. Gibbs
2002-11-18 13:01 ` didier
2002-11-18 13:38 ` Alan Cox
2002-11-20 13:53 ` didier
2002-11-20 14:33 ` Alan Cox
2002-11-20 15:22 ` Simon Burley [this message]
2002-11-20 15:35 ` Mike Dresser
2002-11-20 16:08 ` Alan Cox
2002-11-18 20:07 ` Andre Hedrick
2002-11-18 23:22 ` Alan Cox
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=3DDBA8A8.F370532E@lipsyncpost.co.uk \
--to=simonb@lipsyncpost.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=didier@ece.gatech.edu \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@vger.kernel.org \
/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.