public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jmerkey <jmerkey@utah-nac.org>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Devices/Partitions over 2TB
Date: Mon, 14 Mar 2005 16:58:31 -0700	[thread overview]
Message-ID: <42362527.6010005@utah-nac.org> (raw)
In-Reply-To: <d14vc7$8cu$2@news.cistron.nl>


You have to ignore the partition table contents for ending cylinder. Use 
the following instead. You also
have to write your own FS or modify the partition code in Linux or you 
won't be able to use the storage. This
config option listed in the previous post only enables 64 bit LBA 
addressing, it does not fix the busted fdisk program
or the problems you will see with the partition tables.

i.e.

SystemDisk[j]->BytesPerSector = bdev_hardsect_size(bdev);
SystemDisk[j]->driveSectors = (LONGLONG)bdev->bd_disk->capacity;
SystemDisk[j]->driveSize = (LONGLONG)
((LONGLONG)bdev->bd_disk->capacity *
SystemDisk[j]->BytesPerSector);
SystemDisk[j]->max_sg_elements = bio_get_nr_vecs(bdev);

the bd_disk->capacity reports the actual drive size, but fdisk ignores it.

Good Luck.

Jeff


Miquel van Smoorenburg wrote:

>In article <200503141644.j2EGiVh0000022634@mudpuddle.cs.wustl.edu>,
>Berkley Shands  <berkley@cs.wustl.edu> wrote:
>  
>
>>I have not found any documentation of efforts to overcome the 2TB
>>partition limit,
>>    
>>
>
>config LBD
>        bool "Support for Large Block Devices"
>        depends on X86 || MIPS32 || PPC32 || ARCH_S390_31 || SUPERH
>        help
>          Say Y here if you want to attach large (bigger than 2TB) discs to
>          your machine, or if you want to have a raid or loopback device
>          bigger than 2TB.  Otherwise say N.
>
>Mike.
>
>-
>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/
>
>  
>


  parent reply	other threads:[~2005-03-15  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 16:44 Devices/Partitions over 2TB Berkley Shands
2005-03-14 21:23 ` Miquel van Smoorenburg
2005-03-14 21:35   ` Randy.Dunlap
2005-03-14 23:58   ` jmerkey [this message]
2005-03-15  4:47     ` Bernd Eckenfels
2005-03-15  4:54       ` jmerkey
2005-03-16 12:16         ` Stephen C. Tweedie
2005-03-16 14:06           ` Lennart Sorensen
2005-03-17 13:07 ` Andries Brouwer

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=42362527.6010005@utah-nac.org \
    --to=jmerkey@utah-nac.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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