I just bought a new 300 gig HD for my Slack computer, I noticed when
reading th docs that came with it that Windows has a 137 gig Barrier
that has to be overcome with software that comes with the drive.

Does Linux have any such barrier to overcome? If so what's the procedure?

Thanks





--
LINUX is simple. It just takes a genius to understand its simplicity.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Widgeteye wrote:
> I just bought a new 300 gig HD for my Slack computer, I noticed when
> reading th docs that came with it that Windows has a 137 gig Barrier
> that has to be overcome with software that comes with the drive.
>
> Does Linux have any such barrier to overcome? If so what's the procedure?

According to the /usr/src/linux/Documentation/filesystems/ext2.txt of the
2.4.29 kernel, an ext2 filesystem can, with a 1Kb blocksize, occupy 2047Gb
without problem. With a 4Kb blocksize, it can occupy up to 16384Gb without
problem, and with an 8Kb blocksize (achievable on a 64bit system), it can
occupy up to 32768Gb. FWIW, the documentation also notes that there "is a 2.4
kernel limit of 2048GB for a single block device".

In other words, Linux has no problem addressing the contents of a 300Gb hard
drive.


- --
Lew Pitcher

Master Codewright & JOAT-in-training | GPG public key available on request
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)

iD8DBQFDi67sagVFX4UWr64RAqzCAKD0jNfoLvloPGE5Rj3Gcl 7K/C6r/wCfSa6L
EuuIGhwTm5JX/SxTyCPqItg=
=8oJx
-----END PGP SIGNATURE-----

On Mon, 28 Nov 2005 20:29:16 -0500, Lew Pitcher <lpitcher@sympatico.ca>
wrote:

-snip-
>In other words, Linux has no problem addressing the contents of a 300Gb hard
>drive.

Amen. I'm copying data to my new 320GB disk right now on Slackware 10.2.



Mark Post

On 2005-11-29, Lew Pitcher <lpitcher@sympatico.ca> wrote:
>
>
> In other words, Linux has no problem addressing the contents of a 300Gb hard
> drive.
>
>
> - --


Thanks Lew Pitcher.

--
LINUX is simple. It just takes a genius to understand its simplicity.

Widgeteye <Widgeteye@widgets.com> wrote:


> I just bought a new 300 gig HD for my Slack computer, I noticed when
> reading th docs that came with it that Windows has a 137 gig Barrier
> that has to be overcome with software that comes with the drive.

> Does Linux have any such barrier to overcome? If so what's the procedure?

> Thanks

In my case yes.
Tried to install a 160GB HD under 10.2 Slackware with the
2.4.31 Kernel. Fdisk only recognizes 137 GB.
With the 2.6 Kernel included in Slack 10.2 fdisk recognizes
the full 160GB. Partitioning and mkfs works.

BUT: A filesystemcheck told me much Buffer-I/O-Error.
Also copying ans reading date are not possible.
I could reproduce this with another brand new HD.
Maybe, it's a problem with the bios of the motherboard.
It's updatet to the newest version. But in some cases
the 137GB-Barrier still exist.

Just my 2 cent.

Peter


--
__________________________________________________ ___________________________
Microsoft has been doing a really bad job on their OS.
Linus Torvalds
__________________________________________________ ___________________________

On Thu, 1 Dec 2005 09:30:11 +0000 (UTC), Peter Herttrich <jk11@rz.uni-karlsruhe.de> wrote:

>Tried to install a 160GB HD under 10.2 Slackware with the
>2.4.31 Kernel. Fdisk only recognizes 137 GB.

Details? dmesg, fdisk -l, error messages and so on, not an
unsupported <slack is broken 'cos I dunno how to drive it> )

Grant.

On Mon, 28 Nov 2005 20:29:16 -0500, Lew Pitcher wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Widgeteye wrote:
>> I just bought a new 300 gig HD for my Slack computer, I noticed when
>> reading th docs that came with it that Windows has a 137 gig Barrier
>> that has to be overcome with software that comes with the drive.
>>
>> Does Linux have any such barrier to overcome? If so what's the procedure?
>
> According to the /usr/src/linux/Documentation/filesystems/ext2.txt of the
> 2.4.29 kernel, an ext2 filesystem can, with a 1Kb blocksize, occupy 2047Gb
> without problem. With a 4Kb blocksize, it can occupy up to 16384Gb without
> problem, and with an 8Kb blocksize (achievable on a 64bit system), it can
> occupy up to 32768Gb. FWIW, the documentation also notes that there "is a 2.4
> kernel limit of 2048GB for a single block device".
>
> In other words, Linux has no problem addressing the contents of a 300Gb hard
> drive.

To add a note to that, often there are BIOS limitations encountered as
well. Linux often (normally, even) overcomes these. I'm typing this
message on a machine whose BIOS sees my 160Gb drive as 137Gb, but once the
system is booted the drive is fully visible and functional.

--
mark south: world citizen, net denizen
echo znexfbhgu2000@lnubb.pb.hx|tr a-z n-za-m

On 2005-12-01, Peter Herttrich <jk11@rz.uni-karlsruhe.de> wrote:
> Widgeteye <Widgeteye@widgets.com> wrote:
>
>
>> I just bought a new 300 gig HD for my Slack computer, I noticed when
>> reading th docs that came with it that Windows has a 137 gig Barrier
>> that has to be overcome with software that comes with the drive.
>
>> Does Linux have any such barrier to overcome? If so what's the procedure?
>
>> Thanks
>
> In my case yes.
> Tried to install a 160GB HD under 10.2 Slackware with the
> 2.4.31 Kernel. Fdisk only recognizes 137 GB.
> With the 2.6 Kernel included in Slack 10.2 fdisk recognizes
> the full 160GB. Partitioning and mkfs works.
>
> BUT: A filesystemcheck told me much Buffer-I/O-Error.
> Also copying ans reading date are not possible.
> I could reproduce this with another brand new HD.
> Maybe, it's a problem with the bios of the motherboard.
> It's updatet to the newest version. But in some cases
> the 137GB-Barrier still exist.
>
> Just my 2 cent.
>
> Peter
>
>


Well I finally got my 300G hardrive installed and had mo problem
whatsoever with linux recognizing all 300G of the drive.

I am using kernel version 2.4.26. I don't understand what the
problem was with yours. But I did nothing except have the BIOS
recognise it and boot.

I want to add that it was extremely easy to move Slack to the new
drive also. I love the way you can just copy the entire OS and
apps over and it runs without a hiccup.

All I had to do was 'cp -a * /newdrive' and I was done except for setting up
fstab and lilo,conf. What a pleasure it is working with Linux.

Widgeteye






--
LINUX is simple. It just takes a genius to understand its simplicity.

Peter Herttrich wrote:
> In my case yes.
> Tried to install a 160GB HD under 10.2 Slackware with the
> 2.4.31 Kernel. Fdisk only recognizes 137 GB.
> With the 2.6 Kernel included in Slack 10.2 fdisk recognizes
> the full 160GB. Partitioning and mkfs works.
>
> BUT: A filesystemcheck told me much Buffer-I/O-Error.
> Also copying ans reading date are not possible.
> I could reproduce this with another brand new HD.
> Maybe, it's a problem with the bios of the motherboard.
> It's updatet to the newest version. But in some cases
> the 137GB-Barrier still exist.

Hmm sounds more like some sort of hardware failure but it could be the
BIOS code, what motherboard is it? Does this occur in any other
operating systems?

Richard