From: dwguest@win.tue.nl (Guest section DW)
To: alan@lxorguk.ukuu.org.uk, dhamm@itserve.com, torvalds@transmeta.com
Cc: linux-kernel@vger.rutgers.edu
Subject: The Linux 64 GiB Limit - was: Re: oops! Should be fdisk broken?
Date: Mon, 25 Jan 1999 23:26:48 +0100 (MET) [thread overview]
Message-ID: <199901252226.XAA20449@wsdw01.win.tue.nl> (raw)
> From: David Hamm <dhamm@itserve.com>
>
> I have an 84g raid unit I'm trying to fdisk. When the computer boots I get
> the following info on the drive.
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 164659200 [80400 MB] [80.4 GB]
> When I fdisk it I get different info and after partitioning and mke2fs the
> dirve only mounts with 14g of space. I know this is a geometry issue but why
> is it an issue? Can fdisk be fixed?
>
> Not if you do not provide any detail at all.
From dhamm@itserve.com Mon Jan 25 16:48:31 1999
From: David Hamm <dhamm@itserve.com>
Disk /dev/sdb: 64 heads, 32 sectors, 14864 cylinders
Aha! Very good. You lost precisely 2^27 sectors, that is 64 GiB,
or, more relevant, 2^16 cylinders.
No surprise, since cylinders is a short.
So, the following should improve things. (Unverified, untested.)
Andries
--- hdreg.h~ Fri Jan 22 16:49:34 1999
+++ hdreg.h Mon Jan 25 23:13:06 1999
@@ -114,7 +114,7 @@
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
- unsigned short cylinders;
+ unsigned long cylinders;
unsigned long start;
};
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~1999-01-25 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199901252226.XAA20449@wsdw01.win.tue.nl \
--to=dwguest@win.tue.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhamm@itserve.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).