From: "Mike Black" <mblack@csi-inc.com>
To: "Anders Henke" <anders.henke@sysiphus.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: using 2 TB in real life
Date: Thu, 12 Dec 2002 07:03:45 -0500 [thread overview]
Message-ID: <029301c2a1d6$85cbe280$f6de11cc@black> (raw)
In-Reply-To: 20021212111237.GA12143@schlund.de
Looks like it's already handled in 2.5.
Here's a patch for 2.4:
http://www.gelato.unsw.edu.au/patches-index.html
----- Original Message -----
From: "Anders Henke" <anders.henke@sysiphus.de>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, December 12, 2002 6:12 AM
Subject: using 2 TB in real life
> I've just added a 1.9 TB array to one of my servers (running 2.4.20,
> the device is an 12bay-IFT IDE-to-Fibre-RAID connected via a
> Qlogic 2300 HBA):
>
> Disk /dev/sdb: 255 heads, 63 sectors, 247422 cylinders
> Units = cylinders of 16065 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 247422 1987417183+ 83 Linux
> [...]
> Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
> SCSI device sdb: -320126976 512-byte hdwr sectors (-163904 MB)
> sdb: sdb1
>
>
> Another array (1.2 TB) gives almost the same effect:
> Disk /dev/sdb: 255 heads, 63 sectors, 157450 cylinders
> Units = cylinders of 16065 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sdb1 1 157450 1264717093+ 83 Linux
> [...]
> Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
> SCSI device sdb: -1765523456 512-byte hdwr sectors (195564 MB)
> sdb: sdb1
>
> These issues arise when using arrays larger than around 0.5 T;
> nevertheless, these devices do work fine with both xfs or ext3,
> it's "just" a cosmetical issue. However, this negative
> values make one feel like Linux isn't truely capable of using up to
> 2 TB of disk devices and so this should be resolved.
> To me it seems that sd.c doesn't know how to calculate the
> correct values for such beasts - any ideas?
>
>
> Regards
>
> Anders
> --
> http://sysiphus.de/
> -
> 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/
next prev parent reply other threads:[~2002-12-12 11:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 11:12 using 2 TB in real life Anders Henke
2002-12-12 12:03 ` Mike Black [this message]
2002-12-12 17:22 ` Bryan O'Sullivan
2002-12-12 17:48 ` Anders Henke
2002-12-12 19:03 ` Bryan O'Sullivan
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 23:15 Andries.Brouwer
2002-12-13 14:43 ` Anders Henke
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='029301c2a1d6$85cbe280$f6de11cc@black' \
--to=mblack@csi-inc.com \
--cc=anders.henke@sysiphus.de \
--cc=linux-kernel@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.